Re: initdb crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Euler Taveira de Oliveira <eulerto(at)yahoo(dot)com(dot)br>
Cc: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: initdb crash
Date: 2004-10-08 19:53:22
Message-ID: 15407.1097265202@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Euler Taveira de Oliveira <eulerto(at)yahoo(dot)com(dot)br> writes:
> Sorry for the delay (I have some trouble with my modem). Attached is
> the initdb and backend bootstrap backtrace. Seems to be something in
> the smgr, I couldn't figure out.

Whatever this is, it's local to your build, because no one else is
seeing the same; we would all be unable to initdb if that path of
control were getting followed in general.

It's hard to tell which of the values in the backtrace to believe and
which not, but the impression I get is that there's some confusion over
whether pg_proc is a shared relation ... which of course it is not, but
passing database = 0 to TablespaceCreateDbspace would only happen if
someone thought it was.

Is it possible your copy of bootparse.c escaped getting updated after
bootparse.y last changed? The values shown for its arguments seem
closer to what would have been passed in the old code than what should
be there today.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message James Robinson 2004-10-08 20:02:26 Thank you ...
Previous Message Andrew Dunstan 2004-10-08 19:48:34 Re: Problem with CIDR data type restrictions