Re: Logging WAL when updating hintbit

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Dilip kumar <dilip(dot)kumar(at)huawei(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Logging WAL when updating hintbit
Date: 2014-01-02 01:59:53
Message-ID: CAB7nPqSRgOqssTxECB05GG9gYyj018BV_KEUwL6z60fw8OW_ng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 2, 2014 at 10:21 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Dec 24, 2013 at 7:31 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>>>> Yep, finding all the code paths with a single keyword is usually a
>>>> good thing. Attached is a purely-aesthetical patch that updates the
>>>> internal variable name to wal_log_hints.
>>>
>>> There are many GUC parameters other than wal_log_hints, that their
>>> names are not the same as the names of their variables. We should
>>> update also them?
>> IMO, this looks hard to accept as some existing extensions would break
>> (even if fix would be trivial) and it would make back-patching more
>> difficult. wal_log_hints is a new parameter though...
>
> That's pretty much how I feel about it as well. It probably wouldn't
> hurt very much to go and rename things like Log_disconnections to
> log_disconnections, but changing NBuffers to shared_buffers would
> doubtless annoy a lot of people. Rather than argue about it, I
> suppose we might as well leave the old ones alone.
>
> But keeping the names consistent for new parameters seems simple
> enough, so I've committed your patch.
Thanks.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-01-02 02:15:46 Re: Show lossy heap block info in EXPLAIN ANALYZE for bitmap heap scan
Previous Message Robert Haas 2014-01-02 01:21:07 Re: Logging WAL when updating hintbit