Message-ID: <6cd3fc0c-1255-4560-b3f7-1444e54054b9@gmail.com>
Date: Mon, 5 Jan 2026 08:08:59 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Correction of RowMark Removal During Sel-Join Elimination
To: David Rowley <dgrowleyml@gmail.com>
Cc: Alexander Korotkov <aekorotkov@gmail.com>,
 Richard Guo <guofenglinux@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
 Greg Sabino Mullane <htamfids@gmail.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 Alexander Lakhin <exclusion@gmail.com>
References: <18c6bd6c-6d2a-419a-b0da-dfedef34b585@gmail.com>
 <CAKAnmmJzSGzTRaLATNZPErByO3-j6MwsK--qPSiRLJi4kB05HQ@mail.gmail.com>
 <e7c8173c-91be-41a3-a390-2ca84fbc5147@gmail.com>
 <CAPpHfdsP_abX5hjnxiRJ6guU9P1FH4EdNTMksoGD05tTG1o9vA@mail.gmail.com>
 <9b10b847-067e-45cf-bbf7-7802b6303fc0@gmail.com>
 <CAPpHfdt+bGtrBT8FnPyiP0hq30p0_dUR192RK7TO2LJdTjHnsQ@mail.gmail.com>
 <CAPpHfdt--907hhUzKRJiBce0_e1NUmU6QFnUAtdag4vWzu62eg@mail.gmail.com>
 <CAPpHfdvAHm59MMagJchKM6ECqr7ompQfdD32MkZz9DD9kXqXAA@mail.gmail.com>
 <CAMbWs49pvuAi0JpgfpYcN1cORmrHVX5fHy4rRKuPZ2ekoempJg@mail.gmail.com>
 <CAMbWs49K+N_naHTHSerYFcUD8oRcrKG+1coAHG_sjRdXg3iXtQ@mail.gmail.com>
 <CAPpHfds95Y3DGESNwpo=dhpcnM-fECMhiTXj_KTSXmWbgC2BtA@mail.gmail.com>
 <CAMbWs4-ObbGGyQeamevzhcgVoDEiUTJQC9-EKVeZqRFs05McdQ@mail.gmail.com>
 <CAApHDvo2N+Zpni4XPeFNo2+Sn2AdBztOHoR+ZboBduwiKQgw4g@mail.gmail.com>
Content-Language: en-US
From: Andrei Lepikhov <lepihov@gmail.com>
In-Reply-To: 
 <CAApHDvo2N+Zpni4XPeFNo2+Sn2AdBztOHoR+ZboBduwiKQgw4g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/6cd3fc0c-1255-4560-b3f7-1444e54054b9%40gmail.com>
Precedence: bulk

On 4/1/26 09:38, David Rowley wrote:
> On Sun, 31 Aug 2025 at 13:04, Richard Guo <guofenglinux@gmail.com> wrote:
>>
>> On Sun, Aug 31, 2025 at 9:50 AM Alexander Korotkov <aekorotkov@gmail.com> wrote:
>>> On Sun, Aug 31, 2025 at 2:51 AM Richard Guo <guofenglinux@gmail.com> 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