Re: Simplifying wal_sync_method

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Simplifying wal_sync_method
Дата
Msg-id 9173.1123535008@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Simplifying wal_sync_method  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: Simplifying wal_sync_method  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Simplifying wal_sync_method  ("Jeffrey W. Baker" <jwbaker@acm.org>)
Список pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> 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

> I don't understand why we support so many values.

Because there are so many platforms with different subsets of these APIs
and different performance characteristics for the ones they do have.

> It seems 'fsync' should be fdatasync(), and if that is not available,
> fsync().

I have yet to see anyone do any systematic testing of the different
options on different platforms.  In the absence of hard data, proposing
that we don't need some of the options is highly premature.

> In fact, 8.1 uses O_DIRECT if available,

That's a decision that hasn't got a shred of evidence to justify
imposing it on every platform.
        regards, tom lane


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

Предыдущее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: shrinking the postgresql.conf
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Simplifying wal_sync_method