Re: Inconsistency in extended-query-protocol logging - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Inconsistency in extended-query-protocol logging
Date
Msg-id 12459.1158162725@sss.pgh.pa.us
Whole thread Raw
In response to Re: Inconsistency in extended-query-protocol logging  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Responses Re: Inconsistency in extended-query-protocol logging  ("Guillaume Smet" <guillaume.smet@gmail.com>)
List pgsql-hackers
"Guillaume Smet" <guillaume.smet@gmail.com> writes:
> IMHO, it's more logical to remove it as the text after statement: is
> not a statement in the extended query protocol case.

Well, I was never particularly enamored of the idea that we should put
statement: into everything generated by log_statement.  My proposal
would be to generate
statement: querystring            Simple Queryparse <stmt>: querystring        Parsebind <stmt>/<portal>: querystring
Bindexecute <stmt>/<portal>: querystring    Execute
 

or these prefixed with "duration: xxx", as appropriate.  Bruce was
pretty hot about having statement: in there, so the hard part might
be to convince him.

Also, the current code distinguishes a "fetch" from an
already-partially-executed portal ... do you care about that?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Albe Laurenz"
Date:
Subject: Re: [PATCHES] Linking on AIX (Was: Fix linking of OpenLDAP libraries )
Next
From: "Guillaume Smet"
Date:
Subject: Re: Inconsistency in extended-query-protocol logging