X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0DE1552A4C for ; Mon, 11 Apr 2005 13:42:37 -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 90192-04 for ; Mon, 11 Apr 2005 16:42:31 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 50C17536A6 for ; Mon, 11 Apr 2005 13:42:31 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j3BGgUeF002632; Mon, 11 Apr 2005 12:42:30 -0400 (EDT) To: PFC Cc: pgsql-general@postgresql.org Subject: Re: pg 8.0.1-r3 killls pgadmin3 and phppgadmin In-reply-to: References: <5852.1112819444@sss.pgh.pa.us> <28689.1113150475@sss.pgh.pa.us> <29374.1113228303@sss.pgh.pa.us> <2396.1113236424@sss.pgh.pa.us> Comments: In-reply-to PFC message dated "Mon, 11 Apr 2005 18:32:40 +0200" Date: Mon, 11 Apr 2005 12:42:29 -0400 Message-ID: <2631.1113237749@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/504 X-Sequence-Number: 76417 PFC writes: > I have no idea what to type in gbd to get the trace, though.... What I usually do is - start a psql session - in another window, find out the PID of the backend attached to the psql session, and do $ gdb /path/to/postgres backend_PID ... gdb> b errfinish gdb> cont - go back to psql session and issue problem command - when gdb stops execution, do gdb> bt ... useful printout is here ... gdb> quit sure you want to exit? y regards, tom lane