| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Alexander Goldybin <alexander(at)allieddreams(dot)de> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: deadlocks problem |
| Date: | 2003-05-23 06:46:35 |
| Message-ID: | 20030522234534.R58014-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 16 May 2003, Alexander Goldybin wrote:
> we are using PostgreSQL 7.3.2 for some monthes and are very glad with
> overall perfomance and features of pgSQL !
> But in the last time we experiencing some troubles with deadlocks in
> some tables :-(((. The problem occures from time to time if multiple
> transactions do UPDATE the same table. The found solution (or better
> to say "workaround") for this problem consists of removing all the
> foreign keys in this table. The question now - is there any other
> solution, because this workaround damages the referential integrity of
> the database ? We have tested the transaction isolation level
> SERIALIZEABLE, but with no success. Please help us. Thank you very
> much in advance !!!
You may wish to see recent posts on -hackers re-pointing to a patch that
eliminates one of the locking cases for the foreign keys. It sounds like
it'll be in 7.3.3, but you can try it now and see if it helps the cases
you're working with.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Conxita Marín | 2003-05-23 07:34:51 | Re: Is this a bug? : select '26/10/2003'::date + interval |
| Previous Message | Stephan Szabo | 2003-05-23 06:42:36 | Re: [ADMIN] Q: Structured index - which one runs faster? |