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 CAPpHfdtJqnczQV1Xd66z=cKdd_7s9yF-EQqQeJ4A4he9P4E=jA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18170: Unexpected error: no relation entry for relid 3  (Richard Guo <guofenglinux@gmail.com>)
List 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



pgsql-bugs by date:

Previous
From: Richard Guo
Date:
Subject: Re: BUG #18170: Unexpected error: no relation entry for relid 3
Next
From: PG Bug reporting form
Date:
Subject: BUG #18182: apt distribution is missing for Bionic