Re: Logging WAL when updating hintbit

From: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
To: Florian Weimer <fweimer(at)redhat(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Logging WAL when updating hintbit
Date: 2013-11-15 10:27:15
Message-ID: CAD21AoAjc=Xtw1XC+EMVL+=boPqc=ooa7LAsNEnHW3=9dohUGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 14, 2013 at 7:51 PM, Florian Weimer <fweimer(at)redhat(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2013-11-15 10:31:54 Re: init_sequence spill to hash table
Previous Message Heng Zhi Feng (zheng@hsr.ch) 2013-11-15 10:25:23 Cannot allocate memory