Joel Mc Graw <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
