Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.
От | Amit Kapila |
---|---|
Тема | Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility. |
Дата | |
Msg-id | CAA4eK1+PoH9prMM3p1xsHVSZyfUwXhJ8oi4qXcF+oc-FUi3zAA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility. ("David G. Johnston" <david.g.johnston@gmail.com>) |
Список | pgsql-hackers |
On Wed, Jun 18, 2025 at 10:32 AM David G. Johnston <david.g.johnston@gmail.com> wrote: > >> >> The list can be longer than one or two. We may need to provide similar >> options for other objects, such as replication slots (synced failover >> replication slots on the physical standby), user-defined functions, >> triggers, views, materialized views, operators, policies, etc. And >> then, we would also need 'all' kind of additional option to allow >> cleaning all such objects. The newly formed subscriber may need a few >> of the objects that got replicated on the prior physical standby to >> operate, but not all. >> > > --verb-objecttype=pattern ? (*.* could stand in for all) > For some of the pending cases, like synced replication slots, we will always need to remove all objects, but there could be a few objects for which we need a pattern, as you are suggesting. So, we can think of adding such special switches only for those objects, if required, similar to what pg_dump has for schema or tables. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: