Re: Conflict Detection and Resolution
От | Ajin Cherian |
---|---|
Тема | Re: Conflict Detection and Resolution |
Дата | |
Msg-id | CAFPTHDZVtH39HvTLWqsH+UAZTizjC4OoZTmNzsoZ-bjdxc4qaw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Conflict Detection and Resolution (shveta malik <shveta.malik@gmail.com>) |
Ответы |
Re: Conflict Detection and Resolution
|
Список | pgsql-hackers |
On Wed, Aug 28, 2024 at 2:27 PM shveta malik <shveta.malik@gmail.com> wrote:
2)
Currently pg_dump is dumping even the default resolvers configuration.
As an example if I have not changed default configuration for say
sub1, it still dumps all:
CREATE SUBSCRIPTION sub1 CONNECTION '..' PUBLICATION pub1 WITH (....)
CONFLICT RESOLVER (insert_exists = 'error', update_differ =
'apply_remote', update_exists = 'error', update_missing = 'skip',
delete_differ = 'apply_remote', delete_missing = 'skip');
I am not sure if we need to dump default resolvers. Would like to know
what others think on this.
3)
Why in 002_pg_dump.pl we have default resolvers set explicitly?
In 003_pg_dump.pl, default resolvers are not set explicitly, that is the regexp to check the pg_dump generated command for creating subscriptions. This is again connected to your 2nd question.
regards,
Ajin Cherian
Fujitsu Australia
В списке pgsql-hackers по дате отправления: