| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, konstantin knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
| Subject: | Re: [PATCH] Logical decoding support for sequence advances |
| Date: | 2015-12-15 12:51:43 |
| Message-ID: | 20151215125143.GE17724@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-12-15 12:59:25 | Re: Fixing warnings in back branches? |
| Previous Message | Petr Jelinek | 2015-12-15 12:46:29 | Re: [PATCH] Logical decoding support for sequence advances |