Re: Logging WAL when updating hintbit

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Logging WAL when updating hintbit
Дата
Msg-id CAB7nPqSRgOqssTxECB05GG9gYyj018BV_KEUwL6z60fw8OW_ng@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Logging WAL when updating hintbit  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Thu, Jan 2, 2014 at 10:21 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Tue, Dec 24, 2013 at 7:31 PM, Michael Paquier
> <michael.paquier@gmail.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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Logging WAL when updating hintbit
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Show lossy heap block info in EXPLAIN ANALYZE for bitmap heap scan