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

From Alexander Korotkov
Subject Re: BUG #18170: Unexpected error: no relation entry for relid 3
Date
Msg-id CAPpHfdtzyf_7svV5KW8WgNUZMC4h1VqdbAZUO_OGgaJ74Q6ncA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18170: Unexpected error: no relation entry for relid 3  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: BUG #18170: Unexpected error: no relation entry for relid 3  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-bugs
On Sat, Oct 28, 2023 at 12:12 AM Alexander Korotkov
<aekorotkov@gmail.com> wrote:
>
> On Fri, Oct 27, 2023 at 5:41 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Richard Guo <guofenglinux@gmail.com> writes:
> > > Alternatively, can we look at subroot->parse->targetList instead of
> > > subquery->targetList where we call estimate_num_groups on the output of
> > > the subquery?
> >
> > Please read the comment just above that.
>
> Thank you, Tom,  This is clear.


Hmm...  I just found that I wasn't attentive enough.  The proposed
change is to use subroot->parse->targetList, not
subroot->processed_tlist.  I don't know what could be the problem
here.

------
Regards,
Alexander Korotkov



pgsql-bugs by date:

Previous
From: "下雨天"
Date:
Subject: Re: BUG #18173: ERROR: could not identify a comparison function for type iso-8859-1
Next
From: Tom Lane
Date:
Subject: Re: BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data