Bug #3582

Determine and document which transaction isolation level Pithos backends can and should be run

Added by Georgios Tsoukalas over 8 years ago.

Status:New Start date:04/11/2013
Priority:High Due date:
Assignee:Sofia Papagiannaki % Done:

0%

Category:Pithos Spent time: -
Target version:-

Description

This has to be documented so that Pithos may be deployed correctly.

Right now transactions are set by psycopg according to the connection's
'default_transaction_isolation' which is "read committed" by default
in PostgreSQL's config.

Also take into account that pithos backends are used in more than one
places (e.g. snf-pithos-app, plankton)

SERIALIZABLE may generate more conflicts, while READ COMMITTED needs
FOR UPDATE queries for consistency and deadlock avoidance.


Related issues

related to Synnefo - Feature #3585: Verify etags behaviour is atomic New 04/12/2013

Associated revisions

Revision 480fb416
Added by Sofia Papagiannaki over 8 years ago

pithos: enforce transaction isolation level

Refs: #3582 #3585

Revision 985b9b09
Added by Sofia Papagiannaki about 8 years ago

pithos: enforce transaction isolation level

Refs: #3582 #3585

Also available in: Atom PDF