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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Trying out read streams in pgvector (an extension)
Date: 2025-11-12 04:11:39
Message-ID: CA+hUKGJx6FNqzsxfSOGH0nJZJq1MBc+t7NBKtAmy6zj4HD86tA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Attachment Content-Type Size
0001-Fix-overloaded-remit-of-read_stream_reset.patch text/x-patch 4.5 KB
0002-Add-smoke-test-for-read_stream_resume.patch text/x-patch 5.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-11-12 04:22:09 Re: Issue with logical replication slot during switchover
Previous Message Fujii Masao 2025-11-12 03:48:43 Re: display hot standby state in psql prompt