Re: defer statement logging until after parse

Tom Lane wrote:

>Bruce Momjian <pgman@candle.pha.pa.us> writes:
>
>
>>My idea was to take log_statement, and instead of true/false, have it be
>>all, ddl, mod, or off/none/false(?).  You keep the existing test for
>>log_statement where it is, but test for 'all' now, and after parse, you
>>check for ddl or mod, and print in those cases if the tag matches.
>>
>>
>
>Has any of this discussion taken into account the fact that a
>querystring may contain multiple commands?
>
>
>

It is certainly in my mind - hence the array of parse trees, no?

What does the parser do if one of the statements has an error and the
others are OK? I was (perhaps unwarrantedly) assuming that if you got a
clean return from the parser then none of the statements had a parse error.

cheers

andrew