Re: deadlocks problem

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(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 15:52:56
Message-ID: Pine.LNX.4.33.0305230950230.27073-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 16 May 2003, Alexander Goldybin wrote:

> To Whom It May Concern
> --------------------------------------
>
> Hi,
>
> 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 !!!

To add to what was previously posted, the patch for 7.3.2 is found here:

ftp://ftp.postgresql.org/pub/patches/v7.3.2/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message scott.marlowe 2003-05-23 16:10:39 Re: caching query results
Previous Message scott.marlowe 2003-05-23 15:49:40 Re: Tool for BackUp