DB/clog corruption
От | Reid Thompson |
---|---|
Тема | DB/clog corruption |
Дата | |
Msg-id | F71C0DC6B4FD3648815AAA7F969E35290153081C@sr002-2kexc.ateb.com обсуждение исходный текст |
Ответы |
Re: DB/clog corruption
|
Список | pgsql-general |
I've a db table generating the error below on pg_dump. Per the archives, i've tried creating a clog file 1559 but w/o success ( continue to get the same error) even when i extended the clog file to > 64K. Are there other options to recovering this table? Do i need to extend clog 1559 to a greater size? Do i have to 'do something' to create a non-zero length record at 1/669E0568? ( if so, how?) thanks, reid $ pg_dump -f table_dump.sql -t table_with_error dbname FATAL 2: read of clog file 1559, offset 0 failed: Success pg_dump: FATAL 2: read of clog file 1559, offset 0 failed: Success pg_dump: lost synchronization with server, resetting connection DEBUG: server process (pid 1672) exited with exit code 2 DEBUG: terminating any other active server processes DEBUG: all server processes terminated; reinitializing shared memory and semaphores DEBUG: database system was interrupted at 2005-07-11 08:41:39 EDT DEBUG: checkpoint record is at 1/669E0528 DEBUG: redo record is at 1/669E0528; undo record is at 0/0; shutdown TRUE DEBUG: next transaction id: 1237894; next oid: 2850421 DEBUG: database system was not properly shut down; automatic recovery in progress FATAL 1: The database system is starting up pg_dump: SQL command to dump the contents of table "table_with_error" failed: PQendcopy() failed. pg_dump: Error message from server: FATAL 1: The database system is starting up pg_dump: The command was: COPY "table_with_error" TO stdout; $ DEBUG: ReadRecord: record with zero length at 1/669E0568 DEBUG: redo is not required DEBUG: database system is ready
В списке pgsql-general по дате отправления: