Re: selective statement logging

Andrew Dunstan wrote:
> >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.
> >
> >
> >
>
> If I delay logging until after the parse, these log lines would come out
> in reverse order. Not sure if that matters to anyone, but it might annoy
> me slightly.
>
> line:3 LOG: statement: se4dt ddd;
> line:4 ERROR: syntax error at or near "se4dt" at character 1

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.

--
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