Re: Logging WAL when updating hintbit - Mailing list pgsql-hackers

From Sawada Masahiko
Subject Re: Logging WAL when updating hintbit
Date
Msg-id CAD21AoAjc=Xtw1XC+EMVL+=boPqc=ooa7LAsNEnHW3=9dohUGA@mail.gmail.com
Whole thread Raw
In response to Re: Logging WAL when updating hintbit  (Florian Weimer <fweimer@redhat.com>)
Responses Re: Logging WAL when updating hintbit  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
List pgsql-hackers
On Thu, Nov 14, 2013 at 7:51 PM, Florian Weimer <fweimer@redhat.com> wrote:
> On 11/14/2013 07:02 AM, Sawada Masahiko wrote:
>
>> I attached patch adds new wal_level 'all'.
>
>
> Shouldn't this be a separate setting?  It's useful for storage which
> requires rewriting a partially written sector before it can be read again.
>

Thank you for comment.
Actually, I had thought to add separate parameter.
If so, this feature logs enough information with all of the wal_level
(e.g., minimal) ?
And I thought that relation between wal_lvel and new feature would be
confuse user.

Regards,

-------
Sawada Masahiko



pgsql-hackers by date:

Previous
From: "Heng Zhi Feng (zheng@hsr.ch)"
Date:
Subject: Cannot allocate memory
Next
From: Heikki Linnakangas
Date:
Subject: Re: init_sequence spill to hash table