Re: psql won't stayed connected

Hi Tom,

Thanks for the reply but forgive my ignorance but how do I setup the
debugger breakpoint ?

Regards

Kevin Izzet

Database / Unix Administrator
Tel: (Code)+44(0)1475 655606
Fax: (Code)+44(0)1475 637755
Email: Kevin(dot)Izzet(at)nsc(dot)com

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
05/08/2004 20:13

To: "Kevin Izzet" <Kevin(dot)Izzet(at)nsc(dot)com>
cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] psql won't stayed connected

"Kevin Izzet" <Kevin(dot)Izzet(at)nsc(dot)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

*************************************************************************************
This email may contain confidential and privileged material for the sole
use of the intended recipient. Any review, use, distribution or disclosure
by others is prohibited. If you are not the intended or authorised
recipient please contact the sender by reply email and delete all copies
of this message