Andrew Sullivan <ajs@crankycanuck.ca> writes: > On Thu, Apr 29, 2004 at 03:57:59PM -0400, Andrew Rawnsley wrote: >> I find that some clients (DBVisualizer for one) do exactly that - >> execute the COMMIT;BEGIN sequence, and leaves idle >> transactions on a consistent basis. > Almost all the things I've see that set the autocommit behaviour will > also do this. I suspect it's a pretty common approach. Yeah. We agreed in principle awhile back to "fix" this on the backend side by postponing the actual transaction start until the first command after BEGIN. I looked at this just before 7.4 feature freeze, but decided it wasn't quite trivial and I hadn't time to make it happen. No one's gone back to work on it during the 7.5 cycle either. Right now I'm not wanting to touch that code since both Alvaro and the 2PC guy have open patches against it... regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
