Oliver Jowett <[EMAIL PROTECTED]> writes: > The driver does not actually issue PREPARE or EXECUTE statements; the > server is pretending that the protocol-level Prepare/Bind/Execute > messages are actually something issuing PREPARE/EXECUTE at the SQL level
I had not realized that the logging code recently added to Parse/Bind/Execute deliberately obscures the difference between a Parse message and an SQL PREPARE (etc). This is a terrible decision IMHO and needs to be fixed forthwith. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings