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 22:39:07 |
Message-ID: | 200403102239.i2AMd7G11618@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(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 | Tom Lane | 2004-03-10 22:47:43 | Re: unsafe floats |
Previous Message | Dennis Bjorklund | 2004-03-10 22:37:38 | Re: unsafe floats |