Re: log_min_messages shows debug instead of debug2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
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 15:28:23
Message-ID: 12519.1526484503@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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".
This patch just moves the discrepancy. Still, it's more precise to
print debug2, so I'm okay with changing.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2018-05-16 15:31:28 Re: Considering signal handling in plpython again
Previous Message Robert Haas 2018-05-16 15:27:14 Re: Oddity in COPY FROM handling of check constraints on partition tables