Re: Correction of RowMark Removal During Sel-Join Elimination
От
Andrei Lepikhov
Тема
Re: Correction of RowMark Removal During Sel-Join Elimination
Дата
Msg-id
6cd3fc0c-1255-4560-b3f7-1444e54054b9@gmail.com
Ответ на
Список
Дерево обсуждения
Correction of RowMark Removal During Sel-Join Elimination Andrei Lepikhov <lepihov@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Greg Sabino Mullane <htamfids@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Andrei Lepikhov <lepihov@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Alexander Korotkov <aekorotkov@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Alexander Lakhin <exclusion@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Alexander Korotkov <aekorotkov@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Alexander Korotkov <aekorotkov@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Alexander Korotkov <aekorotkov@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Richard Guo <guofenglinux@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Richard Guo <guofenglinux@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Alexander Korotkov <aekorotkov@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Richard Guo <guofenglinux@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Andrei Lepikhov <lepihov@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination David Rowley <dgrowleyml@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Andrei Lepikhov <lepihov@gmail.com>
Re: Correction of RowMark Removal During Sel-Join Elimination Richard Guo <guofenglinux@gmail.com>
On 4/1/26 09:38, David Rowley wrote: > On Sun, 31 Aug 2025 at 13:04, Richard Guo wrote: >> >> On Sun, Aug 31, 2025 at 9:50 AM Alexander Korotkov wrote: >>> On Sun, Aug 31, 2025 at 2:51 AM Richard Guo wrote: >>>> I think it's better to push this patch sooner rather than later, as >>>> multiple people have encountered the issue in different ways. I'll go >>>> ahead and push 0001 from my patch set shortly. >> >>> I see. You're much farther than I'm. Please, go ahead pushing this. >> >> Done. > > Is there anything left for this thread now? There's still a CF entry > [1] for this. Can the status be updated according to the current > situation? I see the CF entry's tags claim this is a "BugFix" and > "Refactoring Only". It can't be both of those. If work still needs to > be done here, can the tags also be fixed? I checked the thread again, and everything is done. It looks like the 'bugfix' tag was added by mistake, probably because Alexander reported a bug in this thread. Now, the thread covers both refactoring and bug fixing ;). You can pick whichever tag fits best, or leave it as is to mirror the real state. -- regards, Andrei Lepikhov, pgEdge
В списке pgsql-hackers по дате отправления