| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: wal_level in postgresql.conf |
| Date: | 2010-05-14 03:01:00 |
| Message-ID: | AANLkTim8ZJyElYvYJ6nnSFdVoiWCEjSz-gnroJqsW0gN@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 14, 2010 at 12:22 AM, Bruce Momjian <bruce(at)momjian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2010-05-14 03:11:40 | Re: List traffic |
| Previous Message | Fujii Masao | 2010-05-14 02:53:46 | Re: quoting and recovery.conf |