Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally - Mailing list pgsql-bugs

From Richard Guo
Subject Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
Date
Msg-id CAMbWs4_-oUBh7_iybfeCNxFHZf8ADws_zMiSc70jWzoYpSeBYQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Responses Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
List pgsql-bugs
On Wed, Feb 12, 2025 at 10:04 PM Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com> wrote:
> Hmm. The code there assumes that all the Relids will at least have one
> parent each of the children involved. For some reason
> sjinfo->min_lefthand has only relid 1 but not 2 or 5. 2 and 5 are
> actually the parent relids of the children passed in respectively. The
> join is between 2 and 5, then why is 1 appearing in the min_lefthand.
> It might be legitimate, but we need to find the reason. If it's
> legitimate, I think we need to copy the Relids which haven't undergone
> any translation so as to keep them isolated from the parent relids.

Yes, it's legitimate.  For the semijoin, its join clause only
references {1} and {5}, with no other ordering restrictions.
Therefore, the minimum LHS for this join consists only of {1}.

Instead of copying the untranslated Relids and freeing them later, I
think it might be better to modify free_child_join_sjinfo() to avoid
freeing the untranslated members of child_sjinfo.

Thanks
Richard



pgsql-bugs by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
Next
From: Tom Lane
Date:
Subject: Re: BUG #18807: libcrypto.so.1.1: cannot open shared object file