Tracking: support sqitch

[jetjinser]

sqitch is a "Sensible database-native change management for framework-free development and dependable deployment."

sqitch requires the use of features that RisingWave does not yet support:

• pg_try_advisory_lock:
  • mentioned in https://github.com/risingwavelabs/risingwave/issues/112#issuecomment-1930669485
  • sqitch uses this to ensure that only one deployment is running at a time: source code

features used in sqitch tutorials may be commonly used in the sqitch community:

• pg_catalog.has_schema_privilege:
  • already tracked in https://github.com/risingwavelabs/risingwave/issues/11180

[neverchanje]

Thanks. @xiangjinwu Do you think it's possible to support pg_try_advisory_lock? If not, we probably have to implement a standalone driver for sqitch, which would have low ROI in my opinion. We may give up and try to support other tools in the schema migration domain.

As for has_schema_privilege, Redshift, MZ, and CockroachDB all support this function. We should support it too.

[xiangjinwu]

Thanks. @xiangjinwu Do you think it's possible to support pg_try_advisory_lock?

Seems not an easy one: https://github.com/cockroachdb/cockroach/issues/13546

[TennyZhuang]

https://github.com/sqitchers/sqitch/blob/8ee14fb9ec3e14addf84ef2039a09ddb9998e05a/lib/App/Sqitch/Engine.pm#L1102-L1115

It seems that they use the function to ensure only one sqitch instance are attached on the database. Maybe we can perform no-op for a basic usage.

[github-actions[bot]]

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.