Horton

Re: BF mamba failure

Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

View thread View on postgr.es
From: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Kouber Saparev <kouber@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-08-07T05:28:17Z
Lists: pgsql-hackers 
Hi,

On Thu, Aug 07, 2025 at 08:18:26AM +0900, Michael Paquier wrote:
> 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?

I was wondering about adding the "generation" (introduced in 818119afccd3) to
the above error log message, thoughts?

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

Commits

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

  2. Fix race conditions with drop of reused pgstats entries