Re: transaction abort with multiple threads
Joachim Worringen <[email protected]> Wed, 19 May 2010 13:05:41 +0200
| Newsgroups | gmane.comp.python.db.psycopg.devel |
|---|---|
| Organization | IAT GmbH |
| Message-ID | <[email protected]> |
On 05/19/2010 12:44 PM, Joachim Worringen wrote: > None of the threads calls set_isolation_level() (thus, default > transaction control is in place). Actually, the error does not show up when I call db.set_isolation_level(ISOLATION_LEVEL_AUTOCOMMIT) before creating the threads. But as I said, I fear this has negative performance impacts, and just think it shouldn't be necessary (from my understanding). Joachim -- Joachim Worringen Senior Performance Architect International Algorithmic Trading GmbH fon: +49 (0) 40 711 86 75 27 fax: +49 (0) 40 711 86 75 10 Am Knick 8 - D-22113 Oststeinbek Geschäfsführer: Yorck Schumacher - Mirko Stamm - Timo Wagner Gesellschaftssitz: Oststeinbek Registergericht: Lübeck | Registernummer: HRB 7454HL