Re: defer statement logging until after parse

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: defer statement logging until after parse
Date: 2004-03-12 15:18:08
Message-ID: 9306.1079104688@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2004-03-12 15:28:50 Re: defer statement logging until after parse
Previous Message Bruce Momjian 2004-03-12 14:06:02 Re: [HACKERS] notice about costly ri checks (3)