Re: Simplifying wal_sync_method

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Simplifying wal_sync_method
Дата
Msg-id 200508082138.j78LcxQ07547@candle.pha.pa.us
обсуждение исходный текст
Ответ на Re: Simplifying wal_sync_method  (Marko Kreen <marko@l-t.ee>)
Ответы Re: Simplifying wal_sync_method  (Marko Kreen <marko@l-t.ee>)
Re: Simplifying wal_sync_method  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Marko Kreen wrote:
> On Mon, Aug 08, 2005 at 03:56:39PM -0400, Bruce Momjian wrote:
> > Currently, here are the options available for wal_sync_method:
> > 
> >     #wal_sync_method = fsync        # the default varies across platforms:
> >                                     # fsync, fdatasync, fsync_writethrough,
> >                                     # open_sync, open_datasync
> 
> 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.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: Simplifying wal_sync_method
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Simplifying wal_sync_method