initdb crash

On Wed, 6 Oct 2004, Euler Taveira de Oliveira wrote:

Hi,

I saw a initdb crashes when it is creating the template1 database. I
couldn't figure out what is wrong. I attached the backtrace and some
architecture/compiler info.
If someone needs more info, drop me a line.

Can you run initdb with the -d flag?

Also, the directory paths you included suggest that there might be some
old code sitting around. Did you do a make distclean?

Gavin

Hi Gavin,

I saw a initdb crashes when it is creating the template1 database.

I

couldn't figure out what is wrong. I attached the backtrace and

some

architecture/compiler info.
If someone needs more info, drop me a line.

Can you run initdb with the -d flag?

The log is attached.

Also, the directory paths you included suggest that there might be
some
old code sitting around. Did you do a make distclean?

Yes. It's not an old code. That's because i don't like to mix fresh cvs
data with debug data.

=====
Euler Taveira de Oliveira
euler[at]yahoo_com_br

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

On Thu, 7 Oct 2004, Euler Taveira de Oliveira wrote:

Hi Gavin,

I saw a initdb crashes when it is creating the template1 database.

I

couldn't figure out what is wrong. I attached the backtrace and

some

architecture/compiler info.
If someone needs more info, drop me a line.

Can you run initdb with the -d flag?

The log is attached.

Sorry, I meant to ask before: can we get a backtrace from the backend? Ie,
not initdb but from the generated core.

Gavin

Hi Gavin,

I saw a initdb crashes when it is creating the template1

database.

I

couldn't figure out what is wrong. I attached the backtrace and

some

architecture/compiler info.
If someone needs more info, drop me a line.

Can you run initdb with the -d flag?

The log is attached.

Sorry, I meant to ask before: can we get a backtrace from the
backend? Ie,
not initdb but from the generated core.

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.

=====
Euler Taveira de Oliveira
euler[at]yahoo_com_br

_______________________________________________________
Yahoo! Acesso Gr�tis - Internet r�pida e gr�tis. Instale o discador agora! http://br.acesso.yahoo.com/

Euler Taveira de Oliveira <eulerto@yahoo.com.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