Re: selective statement logging - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: selective statement logging
Date
Msg-id 200403102239.i2AMd7G11618@candle.pha.pa.us
Whole thread Raw
In response to Re: selective statement logging  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan wrote:
> >Sure you sure?  I didn't think you would get a tag on a syntax error, so
> >no log would print, which I think is OK.
> >
> >  
> >
> If people are happy with suppressing statement logging on a parse error, 
> OK. For the remainder I would just defer the logging till immediately 
> after the parse and get the tags for the statements - and suppress 
> logging the query string if they were all SELECT or all 
> SELECT|INSERT|UPDATE|DELETE|COPY according to the setting.

Good.  My feeling is that if there is a parse error, we can't be sure
what type of query was sent, and it isn't going to be executed anyway
because it threw an error.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Dennis Bjorklund
Date:
Subject: Re: unsafe floats
Next
From: Tom Lane
Date:
Subject: Re: unsafe floats