From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Timeline following for logical slots |
Date: | 2016-03-31 00:52:34 |
Message-ID: | CAMsr+YEaVbivaBQcZFioYQYicKEBozxMsrS=FSOfRVCj8zmzUQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 31 March 2016 at 07:15, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> > Available attached or at
> >
> https://github.com/2ndQuadrant/postgres/tree/dev/logical-decoding-timeline-following
>
> And pushed this too.
>
Much appreciated. Marked as committed at
https://commitfest.postgresql.org/9/568/ .
This gives us an option for failover of logical replication in 9.6, even if
it's a bit cumbersome and complex for the client, in case failover slots
don't make the cut. And, of course, it's a pre-req for failover slots,
which I'll rebase on top of it shortly.
Andres, I tried to address your comments as best I could. The main one that
I think stayed open was about the loop that finds the last timeline on a
segment. If you think that's better done by directly scanning the List* of
timeline history entries I'm happy to prep a follow-up.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-03-31 00:52:35 | Re: pg_xlogdump fails to handle WAL file with multi-page XLP_FIRST_IS_CONTRECORD data |
Previous Message | Michael Paquier | 2016-03-31 00:43:50 | Re: Very small patch for decode.c |