| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Vik Fearing <vik(at)postgresfriends(dot)org>, zuming(dot)jiang(at)inf(dot)ethz(dot)ch, pgsql-bugs(at)lists(dot)postgresql(dot)org, Alexander Korotkov <akorotkov(at)postgresql(dot)org> |
| Subject: | Re: BUG #18170: Unexpected error: no relation entry for relid 3 |
| Date: | 2023-11-06 07:26:41 |
| Message-ID: | CAMbWs4_STsG1PKQBuvQC8W4sPo3KvML3=jOTjKLUYQuK3g8cpQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 27, 2023 at 1:12 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
Thanks
Richard
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Use-makeNode-instead-of-palloc-to-make-a-UniqueRelInfo-node.patch | application/octet-stream | 1002 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2023-11-06 08:04:34 | Re: BUG #18170: Unexpected error: no relation entry for relid 3 |
| Previous Message | Michael Paquier | 2023-11-06 04:54:31 | Re: BUG #18179: Cluster History Error |