| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mark Gibson <gibsonm(at)cromwell(dot)co(dot)uk> |
| Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>, Joe Conway <mail(at)joeconway(dot)com> |
| Subject: | Re: [GENERAL] dblink - custom datatypes don't work |
| Date: | 2004-02-11 16:39:16 |
| Message-ID: | 21779.1076517556@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-patches |
Mark Gibson <gibsonm(at)cromwell(dot)co(dot)uk> writes:
> I've been trying to use gdb to trace the problem, but I can't work out
> how to attach gdb to a backend process.
It's not hard. Start psql, then in another window use ps to determine
the PID of the connected backend. (The pg_stat_activity view might help
too.) Then
gdb /path/to/postgres-executable PID
gdb> b whereever
gdb> cont
and away you go.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-02-11 16:43:19 | Re: Function parameters of rowtype |
| Previous Message | scott.marlowe | 2004-02-11 16:35:40 | Re: pl/pythonu |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2004-02-11 16:44:06 | Re: [GENERAL] dblink - custom datatypes don't work |
| Previous Message | Mark Gibson | 2004-02-11 16:33:16 | Re: [GENERAL] dblink - custom datatypes don't work |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2004-02-11 16:44:06 | Re: [GENERAL] dblink - custom datatypes don't work |
| Previous Message | Mark Gibson | 2004-02-11 16:33:16 | Re: [GENERAL] dblink - custom datatypes don't work |