Horton

Re: BUG #18170: Unexpected error: no relation entry for relid 3

Alexander Korotkov <aekorotkov@gmail.com>

View thread View on postgr.es
From: Alexander Korotkov <aekorotkov@gmail.com>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Vik Fearing <vik@postgresfriends.org>, zuming.jiang@inf.ethz.ch, pgsql-bugs@lists.postgresql.org, Alexander Korotkov <akorotkov@postgresql.org>
Date: 2023-11-06T08:04:34Z
Lists: pgsql-bugs 
On Mon, Nov 6, 2023 at 9:27 AM Richard Guo <guofenglinux@gmail.com> wrote:
> On Fri, Oct 27, 2023 at 1:12 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>
>> Also, while nosing around in this, I tried to pprint(root) at the
>> point of the error, and got
>>
>> 2023-10-26 12:48:37.852 EDT [1186007] WARNING:  could not dump unrecognized node type: 37413808
>
>
> I came across a similar warning when I tried to pprint(innerrel):
>
>     WARNING:  could not dump unrecognized node type: 0
>
> ... even though we've made UniqueRelInfo be a Node type in commit
> 2b26a69455.
>
> This happens because we use palloc to allocate UniqueRelInfo node in
> innerrel_is_unique_ext(), which I think should be replaced by makeNode.
> Attached is a trivial patch to do so.

Pushed, thank you for catching this.

------
Regards,
Alexander Korotkov

Commits

  1. Disable run condition optimization for some WindowFuncs

  2. Fix allocation of UniqueRelInfo

  3. Make UniqueRelInfo a node

  4. Add "Add trailing commas to enum definitions" to .git-blame-ignore-revs

  5. Remove useless self-joins