On 2026-Apr-07, Amit Kapila wrote:
> I have a question based on 0001's commit message: "This patch adds a
> new option to logical replication output plugin, to declare that it
> does not use shared catalogs (i.e. catalogs that can be changed by
> transactions running in other databases in the cluster).". In which
> cases, currently plugin needs to access multi-database transactions or
> transactions that need to access shared catalogs and on what basis a
> plugin can decide that the changes it requires won't need any such
> access.
I don't think any plugin needs "multi-database" access as such, but
needing access to shared catalogs is likely normal. Repack knows it
won't access any shared catalogs, so it can set the flag at ease.
There's a cross-check added in the commit that tests for access to
shared catalogs if the flag is set to false. I guess you could set it
to false and see what breaks :-)
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
