Re: Assertion failure in pgstat_assert_is_up during walsender exit - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Assertion failure in pgstat_assert_is_up during walsender exit
Date
Msg-id 20220215012344.vlau2mkxcn2qa75p@alap3.anarazel.de
Whole thread Raw
In response to Re: Assertion failure in pgstat_assert_is_up during walsender exit  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Hi,

On 2022-02-14 14:36:12 -0800, Andres Freund wrote:
> On 2022-02-14 15:45:40 -0500, Tom Lane wrote:
> > I tried to replicate the problem described in [1] about logical
> > replication from a v14 source DB to a v11 target.  It fails as
> > described there; I've not yet tracked down why, but it looks like
> > the v11 apply worker fails and closes the connection after sending
> > CREATE_REPLICATION_SLOT.  The v14 walsender doesn't have a problem
> > with that.  However, if I do the same thing using HEAD as the source,
> > I see an assertion failure on the way out of the walsender.  The
> > postmaster log shows
> 
> Gah, sorry, forgot about this one. I'll fix it / apply the fix.

Pushed Sawada-san's fix now. Left the test ([1]) for later, until I can figure
out if the test would be stable on all platforms WRT the duplicated FATAL.

Greetings,

Andres Freund

[1] https://postgr.es/m/20220215012016.lbch4tvpxnm4y7ec%40alap3.anarazel.de



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Postgres 14.2 Windows can't rename temporary statistics file
Next
From: Andres Freund
Date:
Subject: Re: automatically generating node support functions