Thread: 8.0 logging question

8.0 logging question

From
"Ed L."
Date:
In testing slony with pg 8.0 (from cvs), I see a number of these "CONTEXT"
log statements showing up for what appear to be successfully executed
saveplans.  I see the CONTEXT statements are controlled by
log_error_verbosity in postgresql.conf.  I want these CONTEXT log
statements for *errors*, but not for non-error statements.  Is that
possible?

Ed




Re: 8.0 logging question

From
Tom Lane
Date:
"Ed L." <pgsql@bluepolka.net> writes:
> In testing slony with pg 8.0 (from cvs), I see a number of these "CONTEXT"
> log statements showing up for what appear to be successfully executed
> saveplans.  I see the CONTEXT statements are controlled by
> log_error_verbosity in postgresql.conf.  I want these CONTEXT log
> statements for *errors*, but not for non-error statements.  Is that
> possible?

What are these coming from exactly?

There was some discussion about suppressing CONTEXT reports for plpgsql
RAISE NOTICE (and other non-error RAISE levels), but nothing's actually
been done about it yet.

            regards, tom lane

Re: 8.0 logging question

From
"Ed L."
Date:
On Friday September 24 2004 11:45, Ed L. wrote:
>
> They appear to be coming from the saveplan calls in Slony's
> src/backend/slony1_funcs.c (attached) for sl_log_1 and sl_log_2.  Jan
> says "you never see the real execution of saved SPI plans in the log."
> Here's what I see in my log resulting from a simple insert with
> log_error_verbosity = default and logging all:

Correction, that's with log_statement = 'mod'.

On a related note, I see that even though I have log_statement = 'mod' and
log_duration = 'true', we are logging the durations for all queries, not
just those that modify data.  That doesn't make much sense; there is no
information there to know what the duration was for.

Ed