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

From Sawada Masahiko
Subject Re: Logging WAL when updating hintbit
Date
Msg-id CAD21AoBNXDTYjGg9dEE4ic9cgOEf0FPBxPnAS7Puy4JVrgoQTg@mail.gmail.com
Whole thread Raw
In response to Re: Logging WAL when updating hintbit  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Logging WAL when updating hintbit  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Wed, Nov 27, 2013 at 2:28 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Peter Eisentraut <peter_e@gmx.net> writes:
>> On 11/25/13, 7:02 AM, Sawada Masahiko wrote:
>>> I attached the new version patch which adds separated parameter
>>> 'enable_logging_hintbit'.
>
>> Let's not add more parameters named enable_*.  Every parameter enables
>> something.
>
> More to the point: there's a convention that we use enable_foo
> for planner control parameters that gate usage of a "foo" plan type.
> This is not in that category.
>

Thank you for feedback.
I attached the v4 patch which have modified. Just name changed to
'wal_log_hintbtis'.
And i'm also implementing documentation patch.

Regards,

-------
Sawada Masahiko

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: lock on object is already held
Next
From: Michael Paquier
Date:
Subject: Re: Logging WAL when updating hintbit