| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: selective statement logging |
| Date: | 2004-03-10 20:47:52 |
| Message-ID: | 200403102047.i2AKlq316374@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2004-03-10 21:01:25 | Re: PITR Functional Design v2 for 7.5 |
| Previous Message | Jan Wieck | 2004-03-10 20:44:48 | Re: Slony-I makes progress |