Re: 64 bit PostgreSQL 8.3.6 build on AIX 5300-09-02-0849 with IBM XL C/C++ 10.1.0.1 - initdb fails (could not dump unrecognized node type: 650)

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: 64 bit PostgreSQL 8.3.6 build on AIX 5300-09-02-0849 with IBM XL C/C++ 10.1.0.1 - initdb fails (could not dump unrecognized node type: 650)
Дата
Msg-id
893.1234162691@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Re: 64 bit PostgreSQL 8.3.6 build on AIX 5300-09-02-0849 with IBM XL C/C++ 10.1.0.1 - initdb fails (could not dump unrecognized node type: 650) Tom Lane <tgl@sss.pgh.pa.us>
Re: 64 bit PostgreSQL 8.3.6 build on AIX 5300-09-02-0849 with IBM XL C/C++ 10.1.0.1 - initdb fails (could not dump unrecognized node type: 650) Zeugswetter Andreas OSB sIT <Andreas.Zeugswetter@s-itsolutions.at>
RE: [HACKERS] 64 bit PostgreSQL 8.3.6 build on AIX 5300-09-02-0849 with IBM XL C/C++ 10.1.0.1 - initdb fails (could not dump unrecognized node type: 650) Zeugswetter Andreas OSB sIT <Andreas.Zeugswetter@s-itsolutions.at>
Mihai Criveti  writes:
> creating system views ... WARNING:  could not dump unrecognized node type:
> 650
> WARNING:  could not dump unrecognized node type: 650
> WARNING:  could not dump unrecognized node type: 650
> WARNING:  could not dump unrecognized node type: 650
> WARNING:  could not dump unrecognized node type: 650
> WARNING:  could not dump unrecognized node type: 650
> WARNING:  could not dump unrecognized node type: 650
> WARNING:  could not dump unrecognized node type: 650
> WARNING:  could not dump unrecognized node type: 650
> WARNING:  could not dump unrecognized node type: 650
> WARNING:  could not dump unrecognized node type: 650
> FATAL:  badly formatted node string "} {} {} {} {} {} {} {} {} {} {})"...

My, that's interesting.  A look at nodes.h shows that 650 == T_Value,
which simply should not ever occur as a live node type.  Unless my grep
is missing something, T_Value itself is never directly referenced
anywhere in the 8.3 source code.  There are five occurrences of
makeNode(Value) but each of them immediately overwrites the node type
field with another type code such as T_Integer or T_String.

Not to put too fine a point on it, but I'm thinking "compiler bug".
You might try a build with the optimization level backed off to see
if the problem goes away.
		regards, tom lane

В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
FAQ