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)

From: Mihai Criveti <cmihai(at)boreas(dot)ro>
To: pgsql-hackers(at)postgresql(dot)org
Subject: 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)
Date: 2009-02-09 01:24:19
Message-ID: 22c159aa0902081724l84db1acq2e7d5d856b5400c4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

CC="xlC_r -q64" \
CXX="xlC_r -q64" \
AR="ar -X64" \
OBJECT_MODE=64 \
PATH=/usr/bin:/usr/vacpp/bin
./configure
make

Make builds fine, but pg_regress: initdb fails. src/test/regress/log reads:

Running in noclean mode. Mistakes will not be cleaned up.
The files belonging to this database system will be owned by user "cmihai".
This user must also own the server process.

The database cluster will be initialized with locale C.
The default database encoding has accordingly been set to SQL_ASCII.
The default text search configuration will be set to "english".

creating directory
/home/cmihai/build/postgresql-8.3.6/src/test/regress/./tmp_check/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers/max_fsm_pages ... 32MB/204800
creating configuration files ... ok
creating template1 database in
/home/cmihai/build/postgresql-8.3.6/src/test/regress/./tmp_check/data/base/1
... ok
initializing pg_authid ... ok
initializing dependencies ... ok
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 "} {} {} {} {} {} {} {} {} {} {})"...
STATEMENT: /*
* PostgreSQL System Views
*
* Copyright (c) 1996-2008, PostgreSQL Global Development Group
*
* $PostgreSQL: pgsql/src/backend/catalog/system_views.sql,v 1.48
2008/01/01 19:45:48 momjian Exp $
*/

CREATE VIEW pg_roles AS
SELECT

[[ more code here ]]
LANGUAGE SQL STRICT STABLE;

COMMENT ON FUNCTION ts_debug(text) IS
'debug function for current text search configuration';

child process exited with exit code 1
initdb: data directory
"/home/cmihai/build/postgresql-8.3.6/src/test/regress/./tmp_check/data" not
removed at user's request

make install is successful, but of course, initdb will fail in a similar
manner. (WARNING: could not dump unrecognized node type: 650
FATAL: badly formatted node string "} {} {} {} {} {} {} {} {} {} {})"...
after initializing dependencies ... ok).

initdb: 64-bit XCOFF executable or object module not stripped

All commands seem to be work in so far as they don't have missing modules
(ldd) and run. Not much else I can test without a initdb though.

I have found my issue to be similar to
http://archives.postgresql.org/pgsql-ports/2005-06/msg00002.php(unresolved).

Any suggestions / additional tests I can run to pinpoint the problem?

If I use IBM Debugger of AIX, I get right before the crash:

creating system views ...
exec() -> sh
exec() -> postgres
Execution terminated.

So it happens somewhere in postgres code.

--
Criveti Mihai
http://unixsadm.blogspot.com

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2009-02-09 02:23:25 Re: Synch Replication
Previous Message Greg Stark 2009-02-09 00:00:08 Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS