Re: [HACKERS] Replication origins and timelines - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: [HACKERS] Replication origins and timelines
Date
Msg-id CAMsr+YFJRm954TgiQHNcNWwWkenQfNHueZP_EbBzSoXMtyefXQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Replication origins and timelines  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 1 June 2017 at 09:36, Andres Freund <andres@anarazel.de> wrote:
> On 2017-05-31 21:33:26 -0400, Stephen Frost wrote:
>> > This only starts becoming an issue once logical replication slots can
>> > exist on replicas and be maintained to follow the master's slot state.
>> > Which is incomplete in Pg10 (not exposed to users) but I plan to
>> > finish getting in for pg11, making this a possible issue to be
>> > addressed.
>>
>> Fair enough.  I'm disappointed that we ended up with that as the
>> solution for PG10
>
> This has widely been debated, and it's not exactly new that development
> happens incrementally, so I don't have particularly much sympathy for
> that POV.

Yeah. Even if we'd had completed support for decoding on standby,
there's no way we could've implemented the required gymnastics for
getting logical replication to actually use it to support physical
failover for pg10, so it was always going to land in pg11.

This is very much a "how do we do it right when we do do it" topic,
not a pg10 issue.

-- Craig Ringer                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [HACKERS] Replication origins and timelines
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] "create publication..all tables" ignore 'partition notsupported' error