Re: DB failure?

On 8/30/04 11:07 PM, "Wes Palmer" <wespvp(at)syntegra(dot)com> wrote:

> db=> select count(*) from messages;
> ERROR: could not access status of transaction 859000513
> DETAIL: could not open file "/db/pgsql/data/pg_clog/0333": No such file or
> directory
>
> db=> select count(*) from message_recipients;
> ERROR: invalid page header in block 1238604 of relation
> "message_recipients"

Uh, oh.. This would appear to be a big problem... I just tried to do a
pg_dumpall. The server SEGV'd around a Gig into the pg_dumpall:

LOG: server process (PID 12541) was terminated by signal 11
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted at 2004-08-31 07:13:31 MEST
LOG: checkpoint record is at 6E/13A916C
LOG: redo record is at 6E/13A916C; undo record is at 0/0; shutdown FALSE
LOG: next transaction ID: 173895; next OID: 243689524
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: record with zero length at 6E/13A91AC
LOG: redo is not required
LOG: recycled transaction log file "0000006E00000000"
LOG: database system is ready