Re: pg_dump gives segmentation fault and cores

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Doug McNaught <doug(at)wireboard(dot)com>
Cc: replogle992(at)hotmail(dot)com (Andrew Replogle), pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump gives segmentation fault and cores
Date: 2002-02-27 05:11:16
Message-ID: 19805.1014786676@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Doug McNaught <doug(at)wireboard(dot)com> writes:
> replogle992(at)hotmail(dot)com (Andrew Replogle) writes:
>> when trying to run pg_dump dbname > dbname.db it runs for a few
>> minutes then gives the following output as well as a core dump:

> You'll need to rebuild Postgres with debugging turned on, and get a
> backtrace from the core file (type 'bt' at the gdb prompt).

Another useful thing to do is to turn on query logging: do
export PGOPTIONS="-d2"
(or equivalent csh syntax if you prefer a csh-type shell) before
you run pg_dump. Then look in the postmaster log file to see the
queries pg_dump generated. The last two or three queries before
the crash will be useful info.

> What version is this?

Also critical info...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-02-27 05:16:39 Re: configure --with-pam
Previous Message Tom Lane 2002-02-27 05:08:01 Re: pg_dumpall storing multiple copies of DB's?