Tom Lane wrote:
> brian <brian@zijn-digital.com> writes:
>
>>Sorry--i hadn't had time to run a test. Setting it to 'all' works fine,
>>and i think i see the problem: the second INSERT is in a prepared
>>statement, so it's not being logged.
>
>
>>PREPARE mdb2_statement_pgsql00fb05c2c509aa2608b68bf2b87693a2 AS INSERT
>>INTO ...
>
>
> I'm betting that's really a Parse protocol message, not a PREPARE
> statement as such (the 8.1 logging code misguidedly tries to obscure the
> difference). The logging of the subsequent Bind/Execute messages is
> really weak in existing releases :-(. We've fixed it up for 8.2 though.
>
You mean, because the PREPARE .. AS INSERT is different from the actual
EXECUTE statement that follows it? And the latter isn't flagged as a
"mod" action?
In any case, i guess it's not really a big deal. It just seemed
mysterious why the second one wasn't showing up.
b
