I find that some clients (DBVisualizer for one) do exactly that - execute the COMMIT;BEGIN sequence, and leaves idle
transactions on a consistent basis.
On Apr 29, 2004, at 3:19 PM, Andrew Sullivan wrote:
On Thu, Apr 29, 2004 at 02:04:47PM -0400, Jon Pastore wrote:--------------------pgsql thought there was a transaction in progress and was waiting for it to complete when in fact the commit had already taken place.
Come again? That doesn't sound possible. What ismore likely is that somebody issues COMMIT;BEGIN; all at once. You get one transaction through, but you still end up idle in transaciton.
A
-- Andrew Sullivan | ajs@crankycanuck.ca
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
Andrew Rawnsley President The Ravensfield Digital Resource Group, Ltd. (740) 587-0114 www.ravensfield.com
---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
