| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Marko Kreen <marko(at)l-t(dot)ee>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Simplifying wal_sync_method |
| Date: | 2005-08-09 00:04:44 |
| Message-ID: | 10591.1123545884@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Marko Kreen wrote:
>> On same topic:
>> http://archives.postgresql.org/pgsql-general/2005-07/msg00811.php
>> Why does win32 PostgreSQL allow data corruption by default?
> It behaves the same on Unix as Win32, and if you have battery-backed
> cache, you don't need writethrough, so we don't have it as default. I
> am going to write a section in the manual for 8.1 about these
> reliability issues.
I thought we had changed the default for Windows to be fsync_writethrough
in 8.1? We didn't have that code in 8.0, but now that we do, it surely
seems like the sanest default.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-09 00:06:13 | Re: PL/pgSQL: SELECT INTO EXACT |
| Previous Message | Tom Lane | 2005-08-08 23:59:00 | Re: Simplifying wal_sync_method |