Skip site navigation (1) Skip section navigation (2)

Re: Problem with initdb

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Frank Illner <Illner(at)lotto-brandenburg(dot)de>
Cc: "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Problem with initdb
Date: 2004-01-19 05:57:23
Message-ID: 21090.1074491843@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Frank Illner <Illner(at)lotto-brandenburg(dot)de> writes:
> [ initdb fails on suse 8.2 ]

That seems quite odd.  I don't know what's going on, but I can suggest
how to find out.  Please rebuild with

	./configure --enable-debug --enable-cassert

Then run the initdb with -n added to the command line.  The segfault
should then leave a "core" file in $PGDATA/base/1 (if not, try again
after doing "ulimit -c unlimited").  Then do

	$ gdb /path/to/postgres-executable $PGDATA/base/1/core
	gdb> bt
	gdb> quit

and send us gdb's output.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2004-01-19 06:18:02
Subject: Re: unique index problems
Previous:From: Ruslan A DautkhanovDate: 2004-01-19 03:52:44
Subject: vacuum inside the transaction

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group