Re: [PATCH] Clear walsender reader pointers after cleanup

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Clear walsender reader pointers after cleanup
Date: 2026-10-14 03:14:28
Message-ID: as7zlMfTkw-4e4rP@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 12, 2026 at 06:30:52PM -0700, Ayush Tiwari wrote:
> The new assertion was meant to catch either streaming path leaving the
> global pointers set after returning. It isn't needed for the fix, so
> I'm fine with dropping it too..

Hmm. I was looking at all that again, and at the end I have moved
the assertion added by 879ad9f90e83 to be checked at the beginning of
the execution of a replication command, extending it to also check
after the logical replication context.

And done as of f2dd2a3bd44e.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2026-10-14 03:15:00 Parallel autovacuum: honor reduced parallel workers after heap scan phase
Previous Message Manu 2026-10-14 02:55:18 Re: UNDO with FILEOPS, and the FLUX table AM