Re: pg 8.0.1-r3 killls pgadmin3 and phppgadmin

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: PFC <lists(at)boutiquenumerique(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg 8.0.1-r3 killls pgadmin3 and phppgadmin
Date: 2005-04-11 16:42:29
Message-ID: 2631.1113237749@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-sql

PFC <lists(at)boutiquenumerique(dot)com> 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2005-04-11 17:01:41 Re: Data Mart with PostgreSQL (Please!)
Previous Message John Liu 2005-04-11 16:42:20 large object table space in version 8

Browse pgsql-sql by date

  From Date Subject
Next Message Carlos Moreno 2005-04-11 20:29:51 Update aborted if trigger function fails?
Previous Message PFC 2005-04-11 16:32:40 Re: pg 8.0.1-r3 killls pgadmin3 and phppgadmin