Re: Skipping logical replication transactions on subscriber side

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Skipping logical replication transactions on subscriber side
Date: 2021-05-27 10:26:33
Message-ID: CAA4eK1+gbUW4_hpH5OQgTT0KwX65mgsYM6S_W9oCnZJOtt7fww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 27, 2021 at 12:01 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>
> On Wed, May 26, 2021 at 6:11 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> >
> > I agree with you that specifying XID could be easier and
> > understandable for users. I was thinking and studying a bit about what
> > other systems do in this regard. Why don't we try to provide conflict
> > resolution methods for users? The idea could be that either the
> > conflicts can be resolved automatically or manually. In the case of
> > manual resolution, users can use the existing methods or the XID stuff
> > you are proposing here and in case of automatic resolution, the
> > in-built or corresponding user-defined functions will be invoked for
> > conflict resolution. There are more details to figure out in the
> > automatic resolution scheme but I see a lot of value in doing the
> > same.
>
> Yeah, I also see a lot of value in automatic conflict resolution. But
> maybe we can have both ways? For example, in case where the user wants
> to resolve conflicts in different ways or a conflict that cannot be
> resolved by automatic resolution (not sure there is in practice
> though), the manual resolution would also have value.
>

Right, that is exactly what I was saying. So, even if both can be done
as separate patches, we should try to design the manual resolution in
a way that can be extended for an automatic resolution system. I think
we can try to have some initial idea/design/POC for an automatic
resolution as well to ensure that the manual resolution scheme can be
further extended.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2021-05-27 10:58:47 Re: logical replication empty transactions
Previous Message Amit Kapila 2021-05-27 10:04:37 Re: Skipping logical replication transactions on subscriber side