Re: selective statement logging - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: selective statement logging
Date
Msg-id 200403102047.i2AKlq316374@candle.pha.pa.us
Whole thread Raw
In response to Re: selective statement logging  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: selective statement logging  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan wrote:
> >Yes, look at how the command tag is grabbed for the PS display, and do
> >the log checks at that point.
> >
> >  
> >
> Yes, I thought about that. But it would delay the logging of statements, 
> and I'm not sure that's a good idea. What would happen on parse errors, 
> for example?

Well, if it is parse error, then we can't know what type of command it
really was.  They could type 'SE9ECT 1' or 'SELECT 1 WH8RE x=1' and both
are not really SELECT commands to me.

--  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: Hannu Krosing
Date:
Subject: Re: Timing of 'SELECT 1'
Next
From: Jan Wieck
Date:
Subject: Re: Slony-I makes progress