Re: log_min_messages shows debug instead of debug2

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Ideriha, Takeshi" <ideriha(dot)takeshi(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: log_min_messages shows debug instead of debug2
Date: 2018-05-16 16:37:48
Message-ID: CA+TgmobTWhCE_k8mKW+S3P4Rizz-4AZcax_9XjDjf0G0fn24Ng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 16, 2018 at 11:28 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Tue, May 15, 2018 at 4:46 AM, Ideriha, Takeshi
>> <ideriha(dot)takeshi(at)jp(dot)fujitsu(dot)com> wrote:
>>> I noticed that if log_min_messages is set to ‘debug2’, it shows ‘debug’
>>> instead of debug2.
>
>> Seems worth changing to me. Anyone else think differently?
>
> I think the current behavior was intentional at some point, probably
> with the idea that if you put in "debug" it should come out as "debug".

Hmm, that's an angle I hadn't considered.

> This patch just moves the discrepancy. Still, it's more precise to
> print debug2, so I'm okay with changing.

OK. Let's see if anyone else has an opinion.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2018-05-16 17:17:38 Re: Memory unit GUC range checks
Previous Message Magnus Hagander 2018-05-16 16:28:43 Re: Postgres 11 release notes