Try
Home   >   mailing lists

Re: [PATCH] avoid double scanning in function byteain - Mailing list pgsql-hackers

From Stepan Neretin
Subject Re: [PATCH] avoid double scanning in function byteain
Date
Msg-id CA+Yyo5TXs0xb8UwCaSY5k1H=NAPpnF14UoJmSEp2Ue8c+fkYig@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] avoid double scanning in function byteain  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses [PATCH] avoid double scanning in function byteain
Re: [PATCH] avoid double scanning in function byteain
List pgsql-hackers
Tree view


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.



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


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 

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: track generic and custom plans in pg_stat_statements
Next
From: "David G. Johnston"
Date:
Subject: [PATCH] avoid double scanning in function byteain