> > > Now thinking about it, the guy had corrupt table, not WAL log. > > > How is WAL->tables synched? Does the 'wal_sync_method' > > > affect it or not? > > > > I *think* it always fsyncs() there as it is now, but I'm > not 100% sure. > > wal_sync_method is also used to flush pages during a > checkpoint, so it could lead to table corruption too, not > just WAL corruption. > > However, on Unix, 99% of corruption is caused by bad disk or RAM.
... or iDE disks with write cache enabled. I've certainly seen more than what I'd call 1% (though I haven't studied it to be sure) that's because of write-cached disks... //Magnus ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
