Re: flood in logs

hubert depesz lubaczewski <depesz@depesz.com> writes:
> On Fri, Oct 10, 2008 at 08:42:02AM -0400, Tom Lane wrote:
>> Mph, so it's an omission in the log_statement code.  You must have
>> log_statement set to mod or ddl on this machine.

> yes. it's ddl. and on the machine that doesn't print the warning - it's
> "none".

Right, we don't bother to call GetCommandLogLevel if the setting is ALL
or NONE, so the oversight isn't exposed by default.

> so, for now i think it's better to set it to 'none' - and wait for
> new release with fix?

Either that or patch it locally.

I wonder if there are any other omissions in that function...

            regards, tom lane