Dear Hackers, > > OK, should we go ahead and split the pg_subscription catalog for v20 > > then? Maybe pg_subscription (shared) and pg_subscription_db (per- > > database)? > > > > +1, though I am not sure of catalog names. We can brainstorm those > during development.
+1. I cannot come up with better idea to resolve the entanglement. I briefly checked the launcher code and it read 7 attributes [1] at least. Not verified, all of them (or except name) can be retained on the shared catalog. If it's ok I can start a separated thread after analyzing bit more with the PoC. [1]: ``` oid dbid name owner retaindeadtuples retentionactive enabled ``` Best regards, Hayato Kuroda FUJITSU LIMITED
