On Tue, Dec 14, 2010 at 5:21 PM, Peter Geoghegan <peter.geoghega...@gmail.com> wrote: > Here's the output I see when $SUBJECT occurs, on a pg freshly built > from git master with --enable-debug and --enable-cassert:
I am suspicious of the fact that you are invoking initdb as ./initdb. Is it possible you're invoking this from the build tree, and there's an installed copy out there that doesn't match, but is getting used? Like maybe in /usr/local/pgsql/bin? > creating template1 database in /var/lib/pgsql/data/base/1 ... ok > initializing pg_authid ... sh: line 1: 23515 Segmentation fault > (core dumped) "/usr/local/pgsql/bin/postgres" --single -F -O -c > search_path=pg_catalog -c exit_on_error=true template1 > /dev/null > child process exited with exit code 139 Can you fire up gdb on this core dump, using "gdb /usr/local/pgsql/bin/postgres /path/to/coredump"? Or, another possibility is to run initdb with --noclean and then run the command, without routing the output to /dev/null: /usr/local/pgsql/bin/postgres" --single -F -O -c search_path=pg_catalog -c exit_on_error=true template1 -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
