"Kevin Izzet" <Kevin.Izzet@nsc.com> writes:
> Managed to get the debugger to work and here are the results, don't
> understand the results mind :-)
> #0 0x08155d55 in proc_exit ()
> #1 0x08161c17 in PostgresMain ()
> #2 0x0813eee0 in BackendFork ()
> #3 0x0813e8d6 in BackendStartup ()
Hmph. Well, AFAICS the only way for PostgresMain to call proc_exit()
directly is if it's seen EOF from the client (ie, connection closure).
So what you've really got is either a broken copy of psql on the Solaris
machine, or some kind of network issue that's causing the connection to
be closed almost immediately after establishment. The latter seems a
bit odd, since at the very least the connection-request packet must have
got through, but ...
If you have strace or ktrace or similar on the Solaris machine, tracing
psql's kernel calls might be revealing. What you want to watch for is
whether psql is exiting with the connection still open, or whether it
receives an EOF indication and then quits.
BTW, what authorization mode are you trying to use for this connection?
You might experiment with some different ones to see if the behavior
changes. Also, what about turning SSL on or off?
regards, tom lane
