Horton
Menu

Re: [PATCH] avoid double scanning in function byteain

David G. Johnston <david.g.johnston@gmail.com>

View thread
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Stepan Neretin <slpmcf@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Steven Niu <niushiji@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, Kirill Reshke <reshkekirill@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-28T06:41:27Z
Lists: pgsql-hackers 
On Sunday, July 27, 2025, Stepan Neretin <slpmcf@gmail.com> wrote:
>
> One small thing: it seems the commit or diff with the final adjustments
> and test additions wasn't attached or linked in the thread. Could you
> please point me to the commit hash or reference? I’d love to take a look at
> the final version.
>

https://www.postgresql.org/message-id/E1ucruM-006yYH-2A@gemulon.postgresql.org

 The pgsql-committers list is searchable.  All commits get sent there.

https://www.postgresql.org/search/?m=1&q=&l=16&d=31&s=d

David J.

Commits

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

  1. Speed up byteain by not parsing traditional-style input twice.