| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <mha(at)sollentuna(dot)net> |
| Cc: | Marko Kreen <marko(at)l-t(dot)ee>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Simplifying wal_sync_method |
| Date: | 2005-08-09 14:53:39 |
| Message-ID: | 200508091453.j79ErdH22558@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander wrote:
> > 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.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2005-08-09 14:56:32 | Re: Simplifying wal_sync_method |
| Previous Message | Bruce Momjian | 2005-08-09 14:52:11 | Re: Simplifying wal_sync_method |