Hi Heikki,
yes the log_min_messages is set to notice. I've just rechecked it.
Vlastimil Havranek
Vl.
Heikki Linnakangas wrote:
> Tom Lane wrote:
>> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
>>> No, you misread the log. There's a parse, bind, and execute for
>>> COMMIT PREPARED for that GID, but only once.
>>
>> Better read it again.
>
> grep "COMMIT PREPARED" /tmp/a | grep execute
>
> database_A SID:496f4f4d.454 16:12:28.000 LOG: execute <unnamed>:
> COMMIT PREPARED '48801_AOiMyUwnZ6MjBA==_Q3ZoYXZyYW5la2pkYmNEU0xpdmU='
> database_B SID:496f4ed7.e04 16:12:28.000 LOG: execute <unnamed>:
> COMMIT PREPARED '48801_AOiMyUwnZ6MjBA==_Q3ZoYXZyYW5la2pkYmNEU1BhcmFt'
> database_A SID:496f4f4d.454 16:12:29.421 LOG: execute <unnamed>:
> COMMIT PREPARED '48801_AF7jVNS8Z6MjBA==_Q3ZoYXZyYW5la2pkYmNEU0xpdmU='
> database_B SID:496f4ed7.e04 16:12:29.421 LOG: execute <unnamed>:
> COMMIT PREPARED '48801_AF7jVNS8Z6MjBA==_Q3ZoYXZyYW5la2pkYmNEU1BhcmFt'
>
> Those are four different GIDs.
>
--
-------------------------------------------------------------
Vlastimil Havránek
Software Developer
xitee k.s. || www.xitee.com || vlastimil.havranek@xitee.com
Phone: office +420 234262342, mobile +420 775366990
-------------------------------------------------------------