Horton

Re: BF mamba failure

Kouber Saparev <kouber@gmail.com>

View thread View on postgr.es
From: Kouber Saparev <kouber@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-08-08T09:04:52Z
Lists: pgsql-hackers 
Indeed, nothing exotic about our replication.

As for the object 4169049057, I am not able to find it anywhere in the
catalogs. Perhaps it was something that was dropped in the meantime.

На чт, 7.08.2025 г. в 2:18 Michael Paquier <michael@paquier.xyz> написа:

> On Mon, Aug 04, 2025 at 01:00:35PM +0300, Kouber Saparev wrote:
> > We just had the same sudden replica shutdown, this time with version
> 17.3.
> >
> > 2025-08-02 22:10:02.229 UTC,,,473966,,67b3d76c.73b6e,14,,2025-02-18
> > 00:42:20 UTC,8111/0,0,FATAL,XX000,"trying to drop stats entry already
> > dropped: kind=relation dboid=16420 objoid=4169049057 refcount=1",,,,,"WAL
> > redo at 6337E/9FF275E8 for Transaction/COMMIT: 2025-08-02
>
> You are close to wraparound for this relation.  Is that vanilla
> streaming replication with heap?
> --
> Michael
>

Commits

  1. Add information about "generation" when dropping twice pgstats entry

  2. Fix race conditions with drop of reused pgstats entries