Re: unable to dump database, toast errors
От | Lonni Friedman |
---|---|
Тема | Re: unable to dump database, toast errors |
Дата | |
Msg-id | 3E8BC078.4000405@vasoftware.com обсуждение исходный текст |
Ответ на | unable to dump database, toast errors (Lonni Friedman <lfriedman@vasoftware.com>) |
Ответы |
Re: unable to dump database, toast errors
Re: unable to dump database, toast errors |
Список | pgsql-general |
Thanks for your reply. Can pgfsck run on a live database, or does it need to be shutdown first? somewhat related, i just scanned through the output from the vacuumdb that i ran, and I found an error related to the artifact_file table: NOTICE: Index pg_toast_302323_idx: NUMBER OF INDEX' TUPLES (86316) IS NOT THE SAME AS HEAP' (86292). Recreate the index. So, i took down the DB, started it in standalone, and ran: reindex INDEX pg_toast_302323_idx but according to the REINDEX dox, i should see a 'REINDEX' if all is well, and i never do, i'm just dumped back to another backend> prompt. Any ideas? On 04/02/03 20:52, Martijn van Oosterhout wrote: > Just for the hell of it, have you tried: > > http://svana.org/kleptog/pgsql/pgfsck.html > > It may help. Let me know if it does. > > Thanks, > > On Wed, Apr 02, 2003 at 08:46:26PM -0800, Lonni Friedman wrote: >> Greetings, >> Apologies if this comes through twice. >> >> I'm running postgresql-7.2.1 on Redhat-7.2, and when attempting to >> perform a dump with the command: >> pg_dump -Ft -b -o DB_NAME > /tmp/db.tar >> >> it chugs away for a few minutes, and then dies with the following error: >> >> pg_dump: dumping out the contents of table artifact_file >> pg_dump: ERROR: unexpected chunk number 0 (expected 1) for toast value >> 7685119 >> pg_dump: lost synchronization with server, resetting connection >> pg_dump: SQL command to dump the contents of table "artifact_file" >> failed: PQendcopy() failed. >> pg_dump: Error message from server: pg_dump: The command was: COPY >> "artifact_file" WITH OIDS TO stdout; >> pg_dump: *** aborted because of error >> >> I've tried running vacuumdb as follows: >> vacuumdb -z -v -a -f >> >> and its come up clean every time, so i'm really at a loss on how to >> resolve this. If it matters, the artifact_file table has 782 rows, and >> is comprised of text and integer datatype columns. >> >> Any suggestions would be greatly appreciated. thanks! >> >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 2: you can get off all lists at once with the unregister command >> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) >
В списке pgsql-general по дате отправления: