Hi,

I've got clients connected to pgsql via ODBC. If they lose their connection
abruptly, all un-committed transactions are automatically rolled-back (I'm
assuming) but is there anything left behind that needs to be cleaned up on
the server side with regards to the uncommitted transaction(s)?

Much thanks!




---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

"A. Mous" <a.mous (AT) shaw (DOT) ca> writes:

No. When the connection goes away, the backend will log an error,
roll back the transaction and exit cleanly.

-Doug

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org

Anytime data changes in Postgres, the old rows are still on the disk.
This is true regardless if the transaction rolls back.

Read in the docs about vacuuming, which is a process that cleans this
up.

Regards,

d.
--
David Helgason,
Business Development et al.,
Over the Edge I/S (http://otee.dk)
Direct line +45 2620 0663
Main line +45 3264 5049

On 10. nov 2004, at 03:38, Doug McNaught wrote:


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly