| From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Kouber Saparev <kouber(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BF mamba failure |
| Date: | 2025-08-07 05:28:17 |
| Message-ID: | aJQ5cV61RxLzat6T@ip-10-97-1-34.eu-west-3.compute.internal |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2025-08-07 06:55:04 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Thomas Munro | 2025-08-07 05:25:17 | Re: index prefetching |