From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Rubio <drubior@tinet.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: Can't login to 8.2.4 if not superuser...
Date: Thu, 06 Sep 2007 10:18:03 -0400
Message-ID: <22268.1189088283@sss.pgh.pa.us> (raw)
In-Reply-To: <46DFAD00.5070907@tinet.org>
References: <46DE594F.30900@tinet.org>
<13068.1189004492@sss.pgh.pa.us>
<46DFAD00.5070907@tinet.org>
Daniel Rubio <drubior@tinet.org> writes:
> Here's the stack trace, I'm not sure this is all you need (it's the
> first time I use gdb) so, tell me if you need more information
> Core was generated by `/aplicacions/postgres/bin/postmaster -D
> /aplicacions/postgres/data'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x001a66b4 in HaveNFreeProcs ()
> (gdb) backtrace
> #0 0x001a66b4 in HaveNFreeProcs ()
> #1 0x0024deb4 in InitPostgres ()
> #2 0x001b1464 in PostgresMain ()
> #3 0x001837f0 in ServerLoop ()
> #4 0x00184cd8 in PostmasterMain ()
> #5 0x001373f8 in main ()
Well, that's pretty darn odd. It looks like you could work around the
crash by setting superuser_reserved_connections to 0, but that doesn't
tell us *why* it's crashing. HaveNFreeProcs, and the data structure
it looks at, are simple enough that it's hard to credit a bug there.
I'm worried that what you've got is really a compiler bug. What
compiler did you build with, and did you use any nondefault CFLAGS?
(pg_config output would be helpful here.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, drubior@tinet.org
Subject: Re: Can't login to 8.2.4 if not superuser...
In-Reply-To: <22268.1189088283@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox