wal_level in postgresql.conf
in [PgSql]
|
Prev: [HACKERS] wal_mode in postgresql.conf
Next: [HACKERS] wal_level and continuous archiving documentation
From: Bruce Momjian on 13 May 2010 11:22 Bruce Momjian wrote: > Why is 'wal_level' listed next to 'fsync' in postgresql.conf? > > #wal_level = 'hot_standby' # minimal, archive, or hot_standby > #fsync = on # turns forced synchronization on or off > #synchronous_commit = on # immediate fsync at commit > #wal_sync_method = fsync # the default is the first option > > Seems it should be in the archiving section. Sorry, subject was wrong. I am asking about 'wal_level'. -- Bruce Momjian <bruce(a)momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Fujii Masao on 13 May 2010 23:01
On Fri, May 14, 2010 at 12:22 AM, Bruce Momjian <bruce(a)momjian.us> wrote: > Bruce Momjian wrote: >> Why is 'wal_level' listed next to 'fsync' in postgresql.conf? >> >> #wal_level = 'hot_standby' # minimal, archive, or hot_standby >> #fsync = on # turns forced synchronization on or off >> #synchronous_commit = on # immediate fsync at commit >> #wal_sync_method = fsync # the default is the first option >> >> Seems it should be in the archiving section. -1 since wal_level affects WAL logging itself, and is to do with not only archiving but also hot standby. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |