Re: psql won't stayed connected

"Kevin Izzet" <Kevin.Izzet@nsc.com> writes:
> Aug  5 17:01:38 uklnx04 postgres[28522]: [230-1] DEBUG:  00000:
> InitPostgres
> Aug  5 17:01:38 uklnx04 postgres[28522]: [230-2] LOCATION:  PostgresMain,
> postgres.c:2639
> Aug  5 17:01:38 uklnx04 postgres[28522]: [231-1] DEBUG:  00000:
> proc_exit(0)
> Aug  5 17:01:38 uklnx04 postgres[28522]: [231-2] LOCATION:  proc_exit,
> ipc.c:95

That's pretty bizarre ... I didn't think there were any code paths that
would get to proc_exit without emitting an error message.

Can you set a debugger breakpoint at proc_exit and see what the call
stack looks like?  (You can slow things down enough to attach to the
backend with gdb by using the -W switch:
    PGOPTIONS="-W 30" psql ...

            regards, tom lane