That certainly doesn't seem acceptable. As Barry points out people will
really be in the dark when their code doesn't work.
--dc--
Oliver Jowett wrote:
> Barry Lind wrote:
>
>> While debugging my other server problem, I noticed that that only the
>> first BEGIN and COMMIT are logged on the server with sql statement
>> logging enabled. It seems that the subsequent transaction control
>> statements are being executed correctly, it is just that they are not
>> being logged by the server. Is this to be expected? If so, it makes
>> debugging a bit difficult as you can't see what commits are really being
>> executed when you have sql statement logging enabled.
>
>
> Yeah, it's a limitation of statement logging. Statements are logged
> only on Parse, not on Bind/Execute. The driver reuses the internal
> BEGIN/COMMIT statements, so only one Parse is done for each. You will
> see the same thing for user queries if they end up using server-side
> prepare.
>
> There should be some past discussion about this in the -hackers archives.
>
> -O
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>
--
Dave Cramer
http://www.postgresintl.com
519 939 0336
ICQ#14675561
