Re: Persist slot invalidations before publishing them

From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Miłosz Bieniek <bieniek(dot)milosz(at)proton(dot)me>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: Persist slot invalidations before publishing them
Date: 2026-08-27 01:30:11
Message-ID: ao+TI4WNe0gKpiP3@bdtpg
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Miłosz,

On Wed, Aug 26, 2026 at 07:24:07PM +0000, Miłosz Bieniek wrote:
> Hi Bertrand
>
> > 3/ I think 0001 should be backpatched down to 14. 14 and 15 would probably need
> > some adaptations though (I did not look in detail yet).
> >
> > 4/ 0002 should be backpatched down to 17, where failover slot synchronization was
> > introduced.
>
> I did a brief review and tried to test these changes locally.

Thanks for looking at it!

> I ran test for PG19 and master, and they passed, but couldn't
> apply patches for PG18 and lower.

Yeah, the back patch versions are not done. I think it's better to discuss the
issue first and agree on what the fix should be on master. Once done the
back patch versions will be prepared based on the agreement.

Regards,

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2026-08-27 01:36:00 Re: [PATCH] Release replication slot on error in SQL-callable slot functions
Previous Message Tender Wang 2026-08-27 01:24:31 Re: More partition pruning bugs with multi-column RANGE partitions