| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Stepan Neretin <slpmcf(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:41:27 |
| Message-ID: | CAKFQuwbz1DJ5njdzCW-QTUNopJfzR2DXRMqjDm4JQPfyUakCQg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2025-07-28 06:41:29 | Re: track generic and custom plans in pg_stat_statements |
| Previous Message | Michael Paquier | 2025-07-28 06:38:20 | Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? |