| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Incorrect calculation of path fraction value in MergeAppend |
| Date: | 2025-05-07 09:26:28 |
| Message-ID: | a367702b-060d-40f2-a6cc-c089b2b7feb7@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/5/2025 11:12, Álvaro Herrera wrote:
> 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/
Yes,
The magic is how it finds a link to the thread. This time it doesn't
find it by link:
https://www.postgresql.org/message-id/c0c19730-7fec-4c78-bff8-b87ee42b709f@gmail.com
or just a thread-id:
c0c19730-7fec-4c78-bff8-b87ee42b709f(at)gmail(dot)com
--
regards, Andrei Lepikhov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2025-05-07 09:38:58 | Re: PostgreSQL 18 Beta 1 release announcement draft |
| Previous Message | Álvaro Herrera | 2025-05-07 09:25:53 | Re: pg_dump does not dump domain not-null constraint's comments |