From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | jmcgraw(at)databill(dot)com |
Cc: | jpmcgraw1(at)cox(dot)net, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_dumpall won't work? |
Date: | 2002-02-21 18:58:26 |
Message-ID: | 8930.1014317906@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Joel Mc Graw <jmcgraw(at)databill(dot)com> writes:
> Tom, I'm afraid I'm not quite the guru I'd like to be; can you (or
> anyone) provide guidance on getting a "debugger backtrace from the
> segfault"?
Find the core file (if there isn't one, maybe you need "ulimit -c unlimited")
and do
gdb /path/to/executable /path/to/corefile
gdb> bt
gdb> quit
Make sure you are selecting the executable that actually generated the
core dump. It was less than clear to me from your report whether the
crash was in pg_dumpall, pg_dump (which it invokes), or on the backend
side. On many platforms file(1) can tell you which program generated
a particular core dump.
BTW, did you say which platform and which PG version this is?
> The following shows the queries after exporting PGOPTIONS="-d2"
No, I meant the queries sent to the backend --- look in the postmaster
log.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Simone Tellini | 2002-02-21 19:03:46 | Re: pg_dumpall and pg_dumps |
Previous Message | Tom Lane | 2002-02-21 18:44:03 | Re: pg_dumpall and pg_dumps |