Re: Assertion failure in pgstat_assert_is_up during walsender exit

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Assertion failure in pgstat_assert_is_up during walsender exit
Date: 2022-02-15 01:23:44
Message-ID: 20220215012344.vlau2mkxcn2qa75p@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-02-15 01:32:46 Re: automatically generating node support functions
Previous Message Andres Freund 2022-02-15 01:20:16 Re: Replication slot drop message is sent after pgstats shutdown.