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

From Thomas Munro
Subject Re: Streaming read-ready sequential scan code
Date
Msg-id CA+hUKG+q=sg+ifx5NRfBdX_EBAeoJC1fSuaYeQXLCYbN-7nKig@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 Fri, Apr 5, 2024 at 4:20 AM Melanie Plageman
<melanieplageman@gmail.com> wrote:
> So, sequential scan does not have per-buffer data. I did some logging
> and the reason most fully-in-SB sequential scans don't use the fast
> path is because read_stream->pending_read_nblocks is always 0.

Hnghghghgh... right, sorry I guessed the wrong reason, it turns out
that I made a fast path just a little too specialised for pg_prewarm.
Working on it...



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Security lessons from liblzma
Next
From: Greg Sabino Mullane
Date:
Subject: Re: Security lessons from liblzma