On Thu, Oct 15, 2026 at 9:56 AM Fujii Masao <[email protected]> wrote: > > On Thu, Oct 15, 2026 at 3:51 PM Manu <[email protected]> wrote: > > The wait isn't needed when the new status is "off" either: a process > > still caching "on" only writes extra logical info, which is safe, the > > same reasoning DisableLogicalDecoding() already uses to emit without > > waiting. > > 0003 looks good to me. I've attached an updated version with revised > comments in UpdateLogicalDecodingStatusEndOfRecovery(), which still > claimed that all processes had updated their XLogLogicalInfo state > before the function returned. > > I think it's better to backpatch this to v19, since commit 67c20979ce7 > introduced the unnecessary barrier wait. Thoughts? > > Barring any objections, I'm thinking to commit it.
Thank you for the patch. It looks good to me, and I agree that it should be backpatched to v19. Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com
