| 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: | [PATCH] avoid double scanning in function byteain |
| Date: | 2025-07-28 07:11:17 |
| Message-ID: | CAKFQuwZodnFn4TVNLoMZMe=aP2_YkXKFg3oC_cZkN2n0_t94uA@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:
> 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.
>
There is a gitweb link included in the Details section. Click that. Or
just read off the first 8 characters of the commit hash in that link and
plug it into your git client.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2025-07-28 07:11:36 | Re: track generic and custom plans in pg_stat_statements |
| Previous Message | Stepan Neretin | 2025-07-28 06:57:10 | Re: [PATCH] avoid double scanning in function byteain |