Bug #3582
Determine and document which transaction isolation level Pithos backends can and should be run
| 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