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

Поиск
Список
Период
Сортировка
От Richard Guo
Тема Re: BUG #18170: Unexpected error: no relation entry for relid 3
Дата
Msg-id CAMbWs4_STsG1PKQBuvQC8W4sPo3KvML3=jOTjKLUYQuK3g8cpQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #18170: Unexpected error: no relation entry for relid 3  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #18170: Unexpected error: no relation entry for relid 3  (Alexander Korotkov <aekorotkov@gmail.com>)
Список pgsql-bugs
Дерево обсуждения

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.

Thanks
Richard
Вложения

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: BUG #18179: Cluster History Error
Следующее
От: Alexander Korotkov
Дата:
Сообщение: Re: BUG #18170: Unexpected error: no relation entry for relid 3