Re: BUG #18170: Unexpected error: no relation entry for relid 3 - Mailing list pgsql-bugs

From Richard Guo
Subject Re: BUG #18170: Unexpected error: no relation entry for relid 3
Date
Msg-id CAMbWs48FTQtO=ARgjbHqz5fYtOhVUAbdEC1PpnMsjsaRsOENeQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18170: Unexpected error: no relation entry for relid 3  (Andrei Lepikhov <a.lepikhov@postgrespro.ru>)
Responses Re: BUG #18170: Unexpected error: no relation entry for relid 3  (Andrei Lepikhov <a.lepikhov@postgrespro.ru>)
List pgsql-bugs

On Mon, Oct 30, 2023 at 10:47 AM Andrei Lepikhov <a.lepikhov@postgrespro.ru> wrote:
On 30/10/2023 09:24, Richard Guo wrote:
> I also have some concerns about this patch.  It requires that
> root->parse remains unchanged during the whole subquery_planner() in
> order to work, which is an implicit constraint we did not have before.

It is not about unchanged; it is about referencing the same query at the
parent and child query blocks. Am I missing something?

Yeah, that's what I meant.  We need to ensure that root->parse
references the same Query structure during the whole subquery_planner()
for this patch to work, which seems hacky, and error-prone for future
development.  If we really want to do so, at least we need to emphasize
this point in the comment of subquery_planner().

Thanks
Richard

pgsql-bugs by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: BUG #18170: Unexpected error: no relation entry for relid 3
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Logical replication is missing block of rows when sending initial sync?