Oliver Jowett wrote:
> I notice that when using the extended query protocol, statement logging
> appears to happen only when a Parse message is received. This is less
> than ideal:
>
> - statements can be logged that are not actually executed (i.e. a
> Parse/Bind with no corresponding Execute).
> - if statements are re-executed without an intervening Parse (i.e.
> Parse/Bind/Execute/Bind/Execute/...), only the first execution is logged.
>
> There's also a lesser problem with using parameterized queries: the
> actual parameter values used in a Bind are not visible. This is the same
> as the PREPARE/EXECUTE case, except that it's more likely to be done
> transparently by the client's interface library (so we can't just tell
> the application developer "don't do that, then!")
>
> Are there any plans to change this? Should I look at making a change
> along the lines of logging the statement on the first Execute of a
> portal, instead of on Parse?
Well, at execute time, we don't have easy access to the original prepare
statement, especially at that stage in the code. Do you see anyway to
improve that?
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073