Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] logging statement levels

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] logging statement levels
Date: 2004-04-06 18:39:01
Message-ID: 4072F945.4040106@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Bruce Momjian wrote:

>Right now we have log_min_error_statement:
>	
>	#log_min_error_statement = panic # Values in order of increasing severity:
>	                                 #   debug5, debug4, debug3, debug2, debug1,
>	                                 #   info, notice, warning, error, panic(off)
>
>which does allow control of printing only statements generating errors,
>which includes syntax errors.  I don't see why this functionality should
>be mixed in with log_statement.
>
>Did you want a 'syntax error' level to log_statement, that would print
>only statements with syntax errors but not other errors?  That doesn't
>seem very useful to me.
>
>  
>

It wasn't my idea, but I thought it was a good one. But it would go 
along with the idea of these settings as a list instead of a hierarchy, 
e.g.:

log_statement = "syntax-errors, ddl, mod"

In fact, I liked it so much that I thought "syntax-errors" should be the 
default instead of "none".

I think I'd prefer that to having it tied to the log_min_error_statement 
level. But I don't care that much.



cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: Josh BerkusDate: 2004-04-06 18:48:28
Subject: Re: Function to kill backend
Previous:From: Bruce MomjianDate: 2004-04-06 18:38:33
Subject: Re: Function to kill backend

pgsql-patches by date

Next:From: Tom LaneDate: 2004-04-06 19:34:57
Subject: Re: Function to kill backend
Previous:From: Bruce MomjianDate: 2004-04-06 18:38:33
Subject: Re: Function to kill backend

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group