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)

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

I'm working on building the dependencies to run a build farm script on it,
may get better debugging results.

In the meantime, I haveanother build with:
./configure --enable-cassert --enable-debug
--with-includes=/opt/freeware/include --with-libraries=/opt/freeware/lib
--enable-thread-safety && gmake
gmake
sudo gmake install

Based on flags I've seen on the build farm configs. It fails in an identical
manner. From what I've seen, initdb execs quite a few things, but fails at
the exec () postgresql:

Here's /usr/local/pgsql/bin/initdb -d -D /usr/local/pgsql/data

[[ .. same as before, but with more debug..]]
DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR,
xid/subid/cid: 0/1/0, nestlvl: 1, children:
DEBUG: start transaction
DEBUG: CommitTransaction
DEBUG: name: unnamed; blockState: STARTED; state: INPROGR,
xid/subid/cid: 1/1/1, nestlvl: 1, children:
DEBUG: commit transaction
DEBUG: StartTransaction
DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR,
xid/subid/cid: 0/1/0, nestlvl: 1, children:
DEBUG: start transaction
DEBUG: CommitTransaction
DEBUG: name: unnamed; blockState: STARTED; state: INPROGR,
xid/subid/cid: 0/1/35, nestlvl: 1, children:
DEBUG: commit transaction
DEBUG: proc_exit(0)
DEBUG: shmem_exit(0)
DEBUG: exit(0)
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

On Mon, Feb 9, 2009 at 4:37 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:

>
> Please try configuring with --enable-debug --enable-cassert
>
> Then if you don't get any more useful information you might need to try
> initdb -d
>
> cheers
>
> andrew
>
>
> Mihai Criveti wrote:
>
>> 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
>>
>>

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-02-09 06:23:35 Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS
Previous Message K, Niranjan (NSN - IN/Bangalore) 2009-02-09 06:08:12 Re: Synch Replication