| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Incorrect calculation of path fraction value in MergeAppend |
| Date: | 2025-05-07 09:12:49 |
| Message-ID: | 202505070912.v5c7wesueyl7@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-May-07, Andrei Lepikhov wrote:
> > If it's not new in pg18, then adding a commitfest entry in the "bug
> > fixes" category is the right thing. I'd suggest to CC the committer and
> > author of the patch that caused the bug; with the amount of traffic in
> > pgsql-hackers these days, it's all but guaranteed that people will miss
> > things.
> Yep, that's what I wanna do. Procedure of adding new entries to commitfest
> has always been close to magic, but at the moment it is not working on my
> laptop at all - indexing issues?
Weird. Are you doing it here?
https://commitfest.postgresql.org/53/new/
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
“Cuando no hay humildad las personas se degradan” (A. Christie)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2025-05-07 09:18:15 | Re: PostgreSQL 18 Beta 1 release announcement draft |
| Previous Message | Fujii Masao | 2025-05-07 09:06:22 | Re: pgsql: Add function to log the memory contexts of specified backend pro |