Re: Persist slot invalidations before publishing them

From: Miłosz Bieniek <bieniek(dot)milosz(at)proton(dot)me>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
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-26 19:24:07
Message-ID: c1xYEcyG6PvNaeTQlBD5VAsH9K1-41RTiB4QdODvpkhvAGANt5S_cPD-GsIN7vLzKvBrMt1p-PD0CelhGl_zqgwLZnTTKPunf3xYiVKWE0U=@proton.me
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
I ran test for PG19 and master, and they passed, but couldn't
apply patches for PG18 and lower.

I'll try dig deeper into this patch later.

Kind regards,
Miłosz Bieniek

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tristan Partin 2026-08-26 19:36:10 Re: Add a Nix flake
Previous Message Masahiko Sawada 2026-08-26 19:16:40 Re: [PATCH] Fix NULL dereference in subscription REFRESH on concurrent DROP