Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables

From: Tender Wang <tndrwang(at)gmail(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Andrei Lepikhov <lepihov(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, ammmkilo(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
Date: 2026-07-30 03:33:40
Message-ID: CAHewXNm1LPuTAONKt=3ZstM4TgOpsPcJW8jka1aY1Z5Jmb8GOQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Alexander,

Alexander Korotkov <aekorotkov(at)gmail(dot)com> 于2026年5月26日周二 03:27写道:
> Please, check the updated patch. Now restrict_infos_logically_equal()
> uses old save/restore approach. Also added guardian comment to
> RestrictInfo. update_eclasses() switched to use
> restrict_infos_logically_equal() to compare RestrictInfos.
>

Richard and I both asked Tom whether we should fix the redundant
filter introduced after SJE, as discussed in [1].
Tom's answer is that this is not something we need to fix. Please see
his replies in [2] and [3].
I think we can close the discussion on this issue.

[1] https://www.postgresql.org/message-id/1186816.1784573544%40sss.pgh.pa.us
[2] https://www.postgresql.org/message-id/3968565.1785170019%40sss.pgh.pa.us
[3] https://www.postgresql.org/message-id/4154377.1785241465%40sss.pgh.pa.us

--
Thanks,
Tender Wang

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Tom Lane 2026-07-30 02:44:56 Re: type coercion of record types