On 12/10/11 12:13 +0200, Cédric Krier wrote: > Hi, > > With the version 9.1 of PostgreSQL, the Serializable Isolation Level [1] has > been completly implemented. As the documentation explains, application that > uses this level must manage to replay the transaction in case of conflict and > this is the purpose of the patch [2]. > But I'm wondering if this isolation level is not to strict for us. I think the > Repeatable Read Isolation Level is enough as we lock tables for some specific > actions like for stock assignation etc. > As an example, I'm able to produce concurrency exception when creating parties > on PostgreSQL 9.1. > I think for performance, we must switch to Repeatable Read (also other backend > doesn't have the serializable isolation level). > > What do you think about?
http://codereview.tryton.org/151006 -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpUcHY00kucf.pgp
Description: PGP signature
