471,092 Members | 1,539 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,092 software developers and data experts.

8.0 logging question


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


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Nov 23 '05 #1
2 1230
"Ed L." <pg***@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

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 23 '05 #2
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
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly

Nov 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by chuck | last post: by
12 posts views Thread by Eric S. Johansson | last post: by
5 posts views Thread by Shiao | last post: by
3 posts views Thread by Lowell Alleman | last post: by
1 post views Thread by ludvig.ericson | last post: by
4 posts views Thread by Matthew Wilson | last post: by
4 posts views Thread by Alexandru Mosoi | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.