Re: Trying out read streams in pgvector (an extension) - Mailing list pgsql-hackers

From Melanie Plageman
Subject Re: Trying out read streams in pgvector (an extension)
Date
Msg-id CAAKRu_ZVxzwRRbxedgb_LtkFaGf78XAbTO9uExvadV2DzaE=Jg@mail.gmail.com
Whole thread Raw
In response to Re: Trying out read streams in pgvector (an extension)  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Trying out read streams in pgvector (an extension)
List pgsql-hackers
On Tue, Nov 11, 2025 at 4:22 PM Thomas Munro <thomas.munro@gmail.com> wrote:
>
> But for now, to fix pgvector's woes, I wonder if it might make sense
> to call this a bug in v18, and back-patch the tiniest possible change.
> Something like what I posted[2] in this thread almost two years ago.
> I don't think it really affects any core code: we use
> read_stream_reset() only in very minimal ways there (I could
> elaborate), and it's quite arguable that the existing policy is wrong
> for them too, but we'd need to confirm that and perhaps think about
> other extensions that might be using it.

If we are worried about regressing other extensions using
read_stream_reset(), we could make the read stream reset which
preserves the distance a different function in backbranches.

- Melanie



pgsql-hackers by date:

Previous
From: Manni Wood
Date:
Subject: Re: Speed up COPY FROM text/CSV parsing using SIMD
Next
From: Rohit Prasad
Date:
Subject: Re: Include extension path on pg_available_extensions