Re: Streaming read-ready sequential scan code - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Streaming read-ready sequential scan code
Date
Msg-id CA+TgmoZN3MZOaKR=X26VVc5=xePg1AmaHuZszf1-QO7CsWrxBQ@mail.gmail.com
Whole thread Raw
In response to Re: Streaming read-ready sequential scan code  (Melanie Plageman <melanieplageman@gmail.com>)
Responses Re: Streaming read-ready sequential scan code
List pgsql-hackers
On Tue, Feb 20, 2024 at 4:35 AM Melanie Plageman
<melanieplageman@gmail.com> wrote:
> I've written three alternative implementations of the actual streaming
> read user for sequential scan which handle the question of where to
> allocate the streaming read object and how to handle changing scan
> direction in different ways.

It's weird to me that the prospect of changing the scan direction
causes such complexity. I mean, why doesn't a streaming read object
have a forget_all_my_previous_requests() method or somesuch?

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: A new message seems missing a punctuation
Next
From: Ranier Vilela
Date:
Subject: Re: POC, WIP: OR-clause support for indexes