X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 452C75E4245 for ; Fri, 6 Aug 2004 11:41:41 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 83966-02 for ; Fri, 6 Aug 2004 14:41:42 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 199A45E4243 for ; Fri, 6 Aug 2004 11:41:35 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i76EffWO011713; Fri, 6 Aug 2004 10:41:41 -0400 (EDT) To: "Kevin Izzet" Cc: pgsql-admin@postgresql.org Subject: Re: psql won't stayed connected In-reply-to: References: Comments: In-reply-to "Kevin Izzet" message dated "Fri, 06 Aug 2004 10:05:09 +0100" Date: Fri, 06 Aug 2004 10:41:41 -0400 Message-ID: <11712.1091803301@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/31 X-Sequence-Number: 14426 "Kevin Izzet" 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