Re: [PATCH] Logical decoding support for sequence advances - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PATCH] Logical decoding support for sequence advances
Date
Msg-id 20151215125143.GE17724@alap3.anarazel.de
Whole thread Raw
In response to Re: [PATCH] Logical decoding support for sequence advances  (Petr Jelinek <petr@2ndquadrant.com>)
Responses Re: [PATCH] Logical decoding support for sequence advances  (Petr Jelinek <petr@2ndquadrant.com>)
List pgsql-hackers
On 2015-12-15 13:46:29 +0100, Petr Jelinek wrote:
> I don't think that approach alone is good enough. It might be ok for
> selective replication where the replication is driven by tables anyway, but
> in general and especially for failover it's not good enough to tell user
> that we handle some sequences and they have to fix the rest manually.

I think it solves roughly 80-90% of all usages of sequences. That's a
significant improvement over the status quo.

I'm not saying it's perfect, just that it's applicable to 9.4, and might
be good enough initially. I'm not arguing against adding sequence
decoding here.


> That's not much different than fixing them all in practice as you
> script it anyway.

If you can easily script it, it's just the same type (sequences owned by
a single column), everything else starts to be a bit more complicated anyway.


Andres



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [PATCH] Logical decoding support for sequence advances
Next
From: Andres Freund
Date:
Subject: Re: Fixing warnings in back branches?