Re: [ADMIN] Still big problems with pg_dump! - Mailing list pgsql-general

From Tom Lane
Subject Re: [ADMIN] Still big problems with pg_dump!
Date
Msg-id 24144.1032275326@sss.pgh.pa.us
Whole thread Raw
In response to Re: [ADMIN] Still big problems with pg_dump!  (Wim <wdh@belbone.be>)
Responses Re: [ADMIN] Still big problems with pg_dump!
List pgsql-general
Wim <wdh@belbone.be> writes:
> Tom Lane wrote:
>> It would be useful to see a stack traceback from the point of the error,
>> if possible.

> I Would like to send a stack traceback, but I need some halp on this
> (never done this before).

> some add. info:

> SELECT relname FROM pg_class WHERE relname like 'pg_%' AND relkind = 'r';
> gives:
> server closed the connection unexpectedly

This should be producing a core file in your database directory
($PGDATA/base/yourdboid/).  With gdb you'd do
    gdb /path/to/postgres-executable /path/to/corefile
    gdb> bt
    gdb> quit
I don't remember the equivalent incantations with Solaris' debugger.

            regards, tom lane

pgsql-general by date:

Previous
From: Wim
Date:
Subject: Re: [ADMIN] Still big problems with pg_dump!
Next
From: Andrew Sullivan
Date:
Subject: Re: [ADMIN] Still big problems with pg_dump!