Re: EmitWarningsOnPlaceholders is too quiet - Mailing list pgsql-hackers

From Tom Lane
Subject Re: EmitWarningsOnPlaceholders is too quiet
Date
Msg-id 24874.1231183906@sss.pgh.pa.us
Whole thread Raw
In response to Re: EmitWarningsOnPlaceholders is too quiet  (Bruce Momjian <bruce@momjian.us>)
Responses Re: EmitWarningsOnPlaceholders is too quiet  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Tom Lane wrote:
>> (I'm actually kind of wondering what the INFO elog level is good for,
>> as this is just about the only use and it seems wrong.)

> +1 for one less logging level.

I rememebered what INFO is for: it's the elevel that VACUUM VERBOSE
uses to ensure that its output gets seen at the client.  (I missed
that in my first grep because vacuum's elog/ereport calls don't use
INFO as a hard-wired elevel.)  So we probably can't get rid of it.
But that makes it even more clear IMHO that EmitWarningsOnPlaceholders
shouldn't be using it.  It's not intended for error/warning types of
uses, but for verbose logging.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Updates of SE-PostgreSQL 8.4devel patches (r1386)
Next
From: "Robert Haas"
Date:
Subject: Re: QuickLZ compression algorithm (Re: Inclusion in the PostgreSQL backend for toasting rows)