Horton

Re: Change ereport level for QueuePartitionConstraintValidation

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread View on postgr.es
From: Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sergei Kornilov <sk@zsrv.org>, David Rowley <david.rowley@2ndquadrant.com>, Thomas Munro <thomas.munro@gmail.com>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>, Amit Langote <langote_amit_f8@lab.ntt.co.jp>, Robert Haas <robertmhaas@gmail.com>
Date: 2019-09-07T23:45:55Z
Lists: pgsql-hackers 
On 2019-Sep-07, Tom Lane wrote:

> I wrote:
> > Or, of course, we could forget the whole thing and switch the output
> > level for these messages to NOTICE instead.  I'm not for that, but
> > now that we see what it'll cost us to have them better hidden, we can
> > at least have an informed debate.
> > Thoughts?
> 
> Hearing no comments, I've pushed that patch, and marked the v12
> open item closed.

I've marked https://commitfest.postgresql.org/24/2076/ committed also.

Thanks,

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Avoid using INFO elevel for what are fundamentally debug messages.

  2. Revert setting client_min_messages to 'debug1' in new tests.