Re: Trying out read streams in pgvector (an extension)

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>

To: Melanie Plageman <melanieplageman@gmail.com>

Cc: "Jonathan S. Katz" <jkatz@postgresql.org>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-11-12T04:11:39Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add read_stream_{pause,resume}()
- 38229cb90516 19 (unreleased) landed

Attachments

0001-Fix-overloaded-remit-of-read_stream_reset.patch (text/x-patch) patch 0001
0002-Add-smoke-test-for-read_stream_resume.patch (text/x-patch) patch 0002

On Wed, Nov 12, 2025 at 12:19 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> On Wed, Nov 12, 2025 at 11:52 AM Melanie Plageman
> <melanieplageman@gmail.com> wrote:
> > 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.

Here is a draft patch like that, that tries to be as small as
possible.  Trying out the name read_stream_resume().