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. 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. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "Pido que me den el Nobel por razones humanitarias" (Nicanor Parra)
