On Sat, Apr 19, 2014 at 03:35:52PM +0200, Andres Freund wrote:
> Hi,
>
> On 2014-04-19 09:27:00 -0400, Bruce Momjian wrote:
> > Can anyone comment on this? I am able reproduce this in head, and the
> > behavior does look odd. I am able to see the error by just doing:
> >
> > SET log_min_error_statement = notice;
> >
> > in a session before calling the functions; I didn't need to modify
> > postgresql.conf. I am not sure even where to start in debugging this.
>
> Aren't CONTEXT messages influenced by log_error_verbosity, rather than
> log_min_error_statement?
Thanks. I was confused by this, and I can see how the user was confused
because of the way the log message appears in the email, though that
might be just cut/past wrapping:
2014-02-11 18:03:42 MSK
pid=6601,user=postgres,db=dbname,host=10.7.170.1(61351) NOTICE: Hello,
Maxim
2014-02-11 18:03:42 MSK
pid=6601,user=postgres,db=dbname,host=10.7.170.1(61351) CONTEXT: SQL
statement "SELECT test_func('Maxim')"
PL/pgSQL function test_call2() line 3 at PERFORM
That "statement" is not generated by log_min_error_statement, but rather
is part of the CONTEXT line.
Using log_error_verbosity=terse does allow the notice to appear in the
logs without the context.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
