Horton

Re: [PATCH] avoid double scanning in function byteain

Stepan Neretin <slpmcf@gmail.com>

View thread
From: Stepan Neretin <slpmcf@gmail.com>
To: "David G. Johnston" <david.g.johnston@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:57:10Z
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 →

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

On Mon, Jul 28, 2025 at 1:41 PM David G. Johnston <
david.g.johnston@gmail.com> wrote:

> 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.
>


Hi David,

Yes, I'm aware of the pgsql-committers archive and I did check there —
thank you for the reminder!

However, I couldn’t find the patch or final diff in either the
pgsql-committers message you linked or as an attachment in the original
thread.

Best regards,
Stepan