Re: failure in 019_replslot_limit

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Subject: Re: failure in 019_replslot_limit
Date: 2023-04-05 18:55:14
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2023-04-05 11:48:53 -0700, Andres Freund wrote:
> Note that a checkpoint started at "17:50:23.787", but didn't finish before the
> database was shut down. As far as I can tell, this can not be caused by
> checkpoint_timeout, because by the time we get to invalidating replication
> slots, we already did CheckPointBuffers(), and that's the only thing that
> delays based on checkpoint_timeout.
> ISTM that this indicates that checkpointer got stuck after signalling
> 344783.
> Do you see any other explanation?

This all sounded vaguely familiar. After a bit bit of digging I found this:

Which seems like it plausibly explains the failed test?


Andres Freund

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2023-04-05 18:55:50 Re: Should vacuum process config file reload more often
Previous Message Andres Freund 2023-04-05 18:48:53 failure in 019_replslot_limit