On Mon, Jul 1, 2024 at 6:54 PM Amit Kapila <amit.kapil...@gmail.com> wrote: > > On Mon, Jul 1, 2024 at 1:35 PM Masahiko Sawada <sawada.m...@gmail.com> wrote: > > > > Setting resolvers at table-level and subscription-level sounds good to > > me. DDLs for setting resolvers at subscription-level would need the > > subscription name to be specified? > > > > Yes, it should be part of the ALTER/CREATE SUBSCRIPTION command. One > idea could be to have syntax as follows: > > ALTER SUBSCRIPTION name SET CONFLICT RESOLVER 'conflict_resolver' FOR > 'conflict_type'; > ALTER SUBSCRIPTION name RESET CONFLICT RESOLVER FOR 'conflict_type'; > > CREATE SUBSCRIPTION subscription_name CONNECTION 'conninfo' > PUBLICATION publication_name [, ...] CONFLICT RESOLVER > 'conflict_resolver' FOR 'conflict_type';
Looks good to me. Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com