Re: Incorrect calculation of path fraction value in MergeAppend

2025-05-07 Thread Tom Lane
=?utf-8?Q?=C3=81lvaro?= Herrera writes: > Weird, that doesn't seem to work very well if you try to search for > stuff. But if you just specify the Message-Id without clicking "search" > then it works. So here you go: > https://commitfest.postgresql.org/patch/5742/ Yeah, that "search" button is

Re: Incorrect calculation of path fraction value in MergeAppend

2025-05-07 Thread Álvaro Herrera
On 2025-May-07, Andrei Lepikhov wrote: > 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-b87ee42b7...@gmail.com > or just a thread-id: > c0c19730-7fec-4c78-bff8-b87ee42b7...@gmail.com We

Re: Incorrect calculation of path fraction value in MergeAppend

2025-05-07 Thread Andrei Lepikhov
On 7/5/2025 09:57, Álvaro Herrera wrote: On 2025-May-07, Andrei Lepikhov wrote: Hi, Because there was no answer to the issue [1], I'll add it to the next commitfest. Feel free to reject it if my logic on choosing the merge append path is wrong. If this is a bug new in pg18, you should add an

Re: Incorrect calculation of path fraction value in MergeAppend

2025-05-07 Thread Andrei Lepikhov
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 pgs

Re: Incorrect calculation of path fraction value in MergeAppend

2025-05-07 Thread Álvaro Herrera
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

Re: Incorrect calculation of path fraction value in MergeAppend

2025-05-07 Thread Álvaro Herrera
On 2025-May-07, Andrei Lepikhov wrote: > Hi, > > Because there was no answer to the issue [1], I'll add it to the next > commitfest. Feel free to reject it if my logic on choosing the merge append > path is wrong. If this is a bug new in pg18, you should add an item to the "open items" list here

Incorrect calculation of path fraction value in MergeAppend

2025-05-06 Thread Andrei Lepikhov
Hi, Because there was no answer to the issue [1], I'll add it to the next commitfest. Feel free to reject it if my logic on choosing the merge append path is wrong. [1] https://www.postgresql.org/message-id/3ca271fa-ca5c-458c-8934-eb148622b...@gmail.com -- regards, Andrei Lepikhov