Re: Conflict Detection and Resolution - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Conflict Detection and Resolution
Date
Msg-id CAD21AoAAyWHk8bYnkNg49GGPQ+7bRbhCubyoCpeOjXZC0DqAGQ@mail.gmail.com
Whole thread Raw
In response to Re: Conflict Detection and Resolution  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Mon, Jul 1, 2024 at 6:54 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Mon, Jul 1, 2024 at 1:35 PM Masahiko Sawada <sawada.mshk@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



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: PostgreSQL does not compile on macOS SDK 15.0
Next
From: Amit Kapila
Date:
Subject: Re: Slow catchup of 2PC (twophase) transactions on replica in LR