Addition to my previous question...
If postgres has trouble recovering the database from the log, is it possible
to skip the recovery step and loose some recent data changes? If the loss is
relatively small, I think it would be acceptable (say we loose all the changes
in the last few hours). Not sure if the vacuum makes this a bigger problem?
Thanks!
--------
My database apparently crashed - don't know how or why. It happend in the
middle of the night so I wasn't around to troubleshoot it at the time. It
looks like it died during the scheduled vacuum.
Here's the log that gets generated when I attempt to bring it back up:
postmaster successfully started
DEBUG: database system shutdown was interrupted at 2002-05-07 09:35:35 EDT
DEBUG: CheckPoint record at (10, 1531023244)
DEBUG: Redo record at (10, 1531023244); Undo record at (10, 1531022908);
Shutdown FALSE
DEBUG: NextTransactionId: 29939385; NextOid: 9729307
DEBUG: database system was not properly shut down; automatic recovery in
progress...
DEBUG: redo starts at (10, 1531023308)
DEBUG: ReadRecord: record with zero len at (10, 1575756128)
DEBUG: redo done at (10, 1575756064)
FATAL 2: write(logfile 10 seg 93 off 15474688) failed: Success
/usr/bin/postmaster: Startup proc 1339 exited with status 512 - abort
Any suggestions? What are my options, other than doing a complete restore of
the DB from a dump (which is not really an option as the backup is not as
recent as it should be).
Thanks!
Bojan
My database apparently crashed - don't know how or why. It happend in the
middle of the night so I wasn't around to troubleshoot it at the time. It
looks like it died during the scheduled vacuum.
Here's the log that gets generated when I attempt to bring it back up:
postmaster successfully started
DEBUG: database system shutdown was interrupted at 2002-05-07 09:35:35 EDT
DEBUG: CheckPoint record at (10, 1531023244)
DEBUG: Redo record at (10, 1531023244); Undo record at (10, 1531022908);
Shutdown FALSE
DEBUG: NextTransactionId: 29939385; NextOid: 9729307
DEBUG: database system was not properly shut down; automatic recovery in
progress...
DEBUG: redo starts at (10, 1531023308)
DEBUG: ReadRecord: record with zero len at (10, 1575756128)
DEBUG: redo done at (10, 1575756064)
FATAL 2: write(logfile 10 seg 93 off 15474688) failed: Success
/usr/bin/postmaster: Startup proc 1339 exited with status 512 - abort
Any suggestions? What are my options, other than doing a complete restore of
the DB from a dump (which is not really an option as the backup is not as
recent as it should be).
Thanks!
Bojan