Re: defer statement logging until after parse - Mailing list pgsql-patches

From Tom Lane
Subject Re: defer statement logging until after parse
Date
Msg-id 9306.1079104688@sss.pgh.pa.us
Whole thread Raw
In response to Re: defer statement logging until after parse  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: defer statement logging until after parse
List pgsql-patches
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?

            regards, tom lane

pgsql-patches by date:

Previous
From: "Andrew Dunstan"
Date:
Subject: Re: defer statement logging until after parse
Next
From: Andrew Dunstan
Date:
Subject: Re: defer statement logging until after parse