The pgdb module appears to leave transactions idle. My understanding is
that this is not a good practice.

In particular, any client connecting with the pgdb module basically
prevents Slony from working. Slony waits for all active transactions to
complete for some of its operations, and that is indefinite if using
pgdb.

Is there a reason it leaves transactions idle? I don't think psycopg2
does that.

Regards,
        Jeff Davis



_______________________________________________
PyGreSQL mailing list
[email protected]
http://mailman.vex.net/mailman/listinfo/pygresql

Reply via email to