Horton
Menu

Re: [PATCH] avoid double scanning in function byteain

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stepan Neretin <slpmcf@gmail.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, 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-28T13:58:08Z
Lists: pgsql-hackers 
Stepan Neretin <slpmcf@gmail.com> writes:
> 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.

Commit is here:

https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=3683af617

The "patch" link on such pages is good if you want a locally-applyable
patch rather than a colorized version.

The "details" link in the email that David pointed you to would also
have gotten you there.

			regards, tom lane

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.