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?
-O
