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

From Nisha Moond
Subject Re: Conflict Detection and Resolution
Date
Msg-id CABdArM40Ft6MK9Frwc4cb4FC-DGhETNhgGVZ1c-4=N-mU4BBuw@mail.gmail.com
Whole thread Raw
In response to Conflict Detection and Resolution  (shveta malik <shveta.malik@gmail.com>)
List pgsql-hackers
On Fri, Sep 27, 2024 at 1:00 PM Peter Smith <smithpb2250@gmail.com> wrote:
>
> Here are some review comments for v14-0001.
> ~~~
> 7.
> +ALTER SUBSCRIPTION <replaceable class="parameter">name</replaceable>
> RESET CONFLICT RESOLVER FOR (<replaceable
> class="parameter">conflict_type</replaceable>)
>
> I can see that this matches the implementation, but I was wondering
> why don't you permit resetting multiple conflict_types at the same
> time. e.g. what if I want to reset some but not ALL?
>

Thank you for your input.
The RESET command was not part of the initial design, and our current
implementation for resetting ALL or a specific 'conflict_type'
effectively serves its purpose.
Allowing the option to reset two or more conflict types in one command
may complicate the implementation. However, if others also feel the
same, we can implement it. Let's wait for others' feedback.

--
Thanks,
Nisha



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: pgindent fails with perl 5.40
Next
From: Fujii Masao
Date:
Subject: Re: Add new COPY option REJECT_LIMIT