Re: Fix ReadStream handling when heap rescan strategy changes

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Fix ReadStream handling when heap rescan strategy changes
Date: 2026-11-18 22:45:54
Message-ID: CAAKRu_aYEYDXhchh0ioBFUQBsquZK+pjzohJ648TRzLLsw2uow@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 18, 2026 at 7:15 AM Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
>
> On Wed, 18 Nov 2026 at 10:47, Bertrand Drouvot
> <bertranddrouvot(dot)pg(at)gmail(dot)com> wrote:
>
> > Thanks for looking at it!
> >
> > Yeah, that makes sense to me. Having initscan() own the reset/end, strategy update,
> > and stream creation makes the ordering clearer (and also avoids the possible double
> > reset).
>
> +1, v2 LGTM.

Thanks for the reports and the review. I've pushed to master and back branches.

- Melanie

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-11-18 23:02:19 Re: Initial table sync copies the whole table when it is no longer published
Previous Message Zsolt Parragi 2026-11-18 22:40:39 Re: Adding a stored generated column without long-lived locks