Обсуждение: pg_dump gives segmentation fault and cores
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: Segmentation fault (core dumped) at which time I run gdb on it with the following output: Core was generated by `pg_dump'. Program terminated with signal 11, Segmentation fault. #0 0x28084b8c in ?? () I am at a loss of what to do. I need to backup my database for fear of some failure in the near future but cannot get past this issue. Any suggestions or direction would greatly be appreciated. Andrew
replogle992@hotmail.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: > > Segmentation fault (core dumped) > > at which time I run gdb on it with the following output: > > Core was generated by `pg_dump'. > Program terminated with signal 11, Segmentation fault. > #0 0x28084b8c in ?? () You'll need to rebuild Postgres with debugging turned on, and get a backtrace from the core file (type 'bt' at the gdb prompt). What version is this? -Doug -- Let us cross over the river, and rest under the shade of the trees. --T. J. Jackson, 1863
Doug McNaught <doug@wireboard.com> writes: > replogle992@hotmail.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