| From: | Stepan Neretin <slpmcf(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Steven Niu <niushiji(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] avoid double scanning in function byteain |
| Date: | 2025-07-28 06:57:10 |
| Message-ID: | CA+Yyo5TXs0xb8UwCaSY5k1H=NAPpnF14UoJmSEp2Ue8c+fkYig@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 28, 2025 at 1:41 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Sunday, July 27, 2025, Stepan Neretin <slpmcf(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-07-28 07:11:17 | [PATCH] avoid double scanning in function byteain |
| Previous Message | Michael Paquier | 2025-07-28 06:46:39 | Re: track generic and custom plans in pg_stat_statements |