From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Izzet <Kevin.Izzet@nsc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: psql won't stayed connected
Date: Fri, 06 Aug 2004 10:41:41 -0400
Message-ID: <11712.1091803301@sss.pgh.pa.us> (raw)
In-Reply-To: <OF8C7AB545.C0FC08C5-ON80256EE8.0031C501-80256EE8.0031E905@nsc.com>
References: <OF8C7AB545.C0FC08C5-ON80256EE8.0031C501-80256EE8.0031E905@nsc.com>
"Kevin Izzet" <Kevin.Izzet@nsc.com> writes:
> Thanks for the reply but forgive my ignorance but how do I setup the
> debugger breakpoint ?
Something like this:
PGOPTIONS="-W 30" psql ...
Use ps to determine PID of backend connected to psql
gdb /path/to/postgres-executable PID-of-backend
gdb> break proc_exit
gdb> continue
(wait for rest of timeout to expire)
gdb will report reaching proc_exit breakpoint
gdb> bt
... interesting result is here ...
gdb> quit
If you've never done this before it will probably take you more than 30
seconds to get into gdb --- adjust the W option accordingly.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, Kevin.Izzet@nsc.com
Subject: Re: psql won't stayed connected
In-Reply-To: <11712.1091803301@sss.pgh.pa.us>
References: <OF8C7AB545.C0FC08C5-ON80256EE8.0031C501-80256EE8.0031E905@nsc.com> <11712.1091803301@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