Z3 PostgreSQL database adapter does not do two-phase commit

Bug #35676 reported by Stuart Bishop
20
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Low
Stuart Bishop

Bug Description

With PostgreSQL 8.1, we can do a proper two phase commit. The existing PostgreSQL database driver does not do this, as the feature did not exist when it was written.

We should update the PostgreSQL database adapter for Zope3 to do a proper two phase commit. Because we are now using multiple data stores (the session database and the primary database), this is important and possibly a dataloss bug. At a minimum, it will cause occasional errors to end users. For example, every time a serialization exception occurs with the session database, changes to the primary database may have already been committed so when Z3 retries the transaction an error will likely be raised.

Dafydd Harries (daf)
Changed in launchpad:
status: Unconfirmed → Confirmed
Stuart Bishop (stub)
description: updated
Revision history for this message
Stuart Bishop (stub) wrote :

Currently psycopg does not provide an API to do this. connection.prepare() needs to be added to upstream (as discussed in the DB-API SIG)

Changed in launchpad:
importance: Medium → Wishlist
Revision history for this message
Stuart Bishop (stub) wrote :

Using Storm

Changed in launchpad:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.