Re: Unresolved repliaction hang and stop problem. - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Unresolved repliaction hang and stop problem.
Date
Msg-id 20210428140636.GA12179@alvherre.pgsql
Whole thread Raw
In response to Re: Unresolved repliaction hang and stop problem.  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Unresolved repliaction hang and stop problem.  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 2021-Apr-28, Amit Kapila wrote:

> On Wed, Apr 28, 2021 at 6:48 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:

> > Hmm ... On what does it depend (other than plain git conflicts, which
> > are aplenty)?  On a quick look to the commit, it's clear that we need to
> > be careful in order not to cause an ABI break, but that doesn't seem
> > impossible to solve, but I'm wondering if there is more to it than that.
> 
> As mentioned in the commit message, we need another commit [1] change
> to make this work.
> 
> [1] - https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c55040ccd0

Oh, yeah, that looks tougher.  (Still not impossible: it adds a new WAL
message type, but we have added such on a minor release before.)

... It's strange that replication worked for them on pg10 though and
broke on 13.  What did we change anything to make it so?  (I don't have
any fish to fry on this topic at present, but it seems a bit
concerning.)

-- 
Álvaro Herrera       Valdivia, Chile



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch
Next
From: Alvaro Herrera
Date:
Subject: Re: pg_hba.conf.sample wording improvement