Subject: Can't login to 8.2.4 if not superuser...
From: tgl@sss.pgh.pa.us (Tom Lane)
Date: 9/5/2007 11:01:32 AM
Daniel Rubio <drubior@tinet.org> writes:
> If I log via psql using the postgres user via psql there's no problem,
> but If I try to log as a different user, the postmaster process hangs
> and I can't connect.
That's not a hang, it's a core dump. Can you get a stack trace with
gdb or local equivalent?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
Subject: Can't login to 8.2.4 if not superuser...
From: tgl@sss.pgh.pa.us (Tom Lane)
Date: 9/6/2007 10:18:03 AM
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
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Subject: Can't login to 8.2.4 if not superuser...
From: tgl@sss.pgh.pa.us (Tom Lane)
Date: 9/7/2007 10:38:40 AM
Daniel Rubio <drubior@tinet.org> writes:
> Using the older gcc version to compile, the problem disappears ...
Hmm. gcc 4.0.4 is hardly new. I'm wondering about the weird CFLAGS and
include/link paths shown in your pg_config output. What does all that
do?
>> CPPFLAGS = -I/sfw10/builds/build/sfw10-patch/usr/src/cmd/postgres/rltmp/include
>> -I/usr/sfw/include
>> CFLAGS = -xO3 -xarch=v8 -xspace -W0,-Lt -W2,-Rcond_elim -Xa -xildoff
>> -xc99=none -xCC
>> LDFLAGS = -L/sfw10/builds/build/sfw10-patch/usr/src/cmd/postgres/rltmp/lib
>> -L/usr/sfw/lib -L/usr/lib -Wl,-R/usr/lib
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
|