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 item to the "open items"
> list here: https://wiki.postgresql.org/wiki/Open_Items The RMT will
> then take over and pester the committer/author to ensure the bug is
> fixed.
It is not a new bug.
>
> 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?
--
regards, Andrei Lepikhov
