On 05/15/2013 11:55 AM, Eric Caudal wrote:
Hi,
We have a case where our procurement scheduler (with
procurement_confirm and action_assign) is blocking other transactions
(such as website synchronization) or vice versa with an error such as
"Serialized Access due to concurrent update".
So far we have made some researches and we discover that this is maybe
due to an error " Repeatable Read Isolation Level", documented here:
http://www.postgresql.org/docs/9.2/static/transaction-iso.html
Hi,
A point to check is the python psycopg module version you are using.
Older versions ( before v2.4.2 ) are not aware of the newer postgresql
transaction levels and map the repeatable read isolation level to the
serializable transaction level which is more strict and less performant.
For more info about this check the comments of the Cursor class in
"openobject-server/openerp/sql_db.py"
Regards,
Jos
--
Jos De Graeve
Apertoso business ICT
Guido Gezellelaan 16 - B-9800 Deinze - Belgium
Direct: +32 9 381 64 50
General: +32 9 386 19 73
Mobile: +32 475 54 68 80
Skype: apertoso
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
