Simplifying wal_sync_method

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Simplifying wal_sync_method
Дата
Msg-id 200508081956.j78Judc22024@candle.pha.pa.us
обсуждение исходный текст
Ответы 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
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.  It seems 'fsync'
should be fdatasync(), and if that is not available, fsync().  Same with
open_sync and open_datasync.

In fact, 8.1 uses O_DIRECT if available, and I don't see why we don't
just use the "data" options automatically if available too, rather than
have users guess which options their OS supports.  We might need an
option to print the actual features used, but I am not sure.

Is this something for 8.1 or 8.2?

--  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: #escape_string_warning = off
Следующее
От: Simon Riggs
Дата:
Сообщение: Re: Solving the OID-collision problem