Continuous archiving fails - Mailing list pgsql-bugs

From David Darville
Subject Continuous archiving fails
Date
Msg-id 20070412121948.GA11523@darville.vm.bytemark.co.uk
Whole thread Raw
Responses Re: Continuous archiving fails
List pgsql-bugs
Hello everybody

While testing a continuous archiving setup using PostgreSQL 8.2.3, on Debian
Etch amd64, I found out that the slave database crashed when I did a 'DROP
DATABASE' on the master.

I was trying to stress test our setup, by continuously restoring a dump of
our database, dropping the database, restoring it etc.
But when I dropped the database I found out that the slave database crased,
leaving log messages like these:

....
LOG: restored log file "000000010000004F000000F0" from archive
LOG: restored log file "000000010000004F000000F1" from archive
LOG: restored log file "000000010000004F000000F2" from archive
LOG: restored log file "000000010000004F000000F3" from archive
LOG: could not fsync segment 0 of relation 19820534/105758957/125593540: No
such file or directory
CONTEXT: xlog redo checkpoint: redo 4F/F3859B60; undo 0/0; tli 1; xid
0/84778; oid 125601021; multi 1; offset 0; online
FATAL: storage sync failed on magnetic disk: No such file or directory
CONTEXT: xlog redo checkpoint: redo 4F/F3859B60; undo 0/0; tli 1; xid
0/84778; oid 125601021; multi 1; offset 0; online
LOG:  startup process (PID 16101) exited with exit code 1
LOG: aborting startup due to startup process failure



---
David Darville

pgsql-bugs by date:

Previous
From: John R Pierce
Date:
Subject: Re: RHEL4 RPM packages
Next
From: Tom Lane
Date:
Subject: Re: Continuous archiving fails