Re: Logging WAL when updating hintbit

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Logging WAL when updating hintbit
Date: 2013-11-26 16:44:08
Message-ID: 5294CFD8.7030301@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Also, I'd be worried about confusion with other log_* and logging_*
parameters, which are about something other than WAL. Maybe it should
be called wal_log_hintbits (or walog_hintbits?).

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Johnston 2013-11-26 16:54:13 Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block
Previous Message Bruce Momjian 2013-11-26 16:29:50 Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block