"Philippe Lang" <[EMAIL PROTECTED]> writes:
> One more question: i'm surprised there are so many ExclusiveLocks when displaying
> pg_lock:
> 6514392 14385 ExclusiveLock t
> 6495858 11439 ExclusiveLock t
> ...etc...
Those are the transaction ID locks.
> I foun
On Mon, Oct 25, 2004 at 05:56:04PM +0200, Philippe Lang wrote:
> One more question: i'm surprised there are so many ExclusiveLocks when
> displaying pg_lock:
>
> 33044 32920 11439 RowExclusiveLockt
> 6514392 14385 ExclusiveLock t
> 6495858 11439
be the
reason?
Philippe
-Message d'origine-
De : Tom Lane [mailto:[EMAIL PROTECTED]
Envoyé : lundi, 25. octobre 2004 16:16
À : Philippe Lang
Cc : [EMAIL PROTECTED]
Objet : Re: [GENERAL] FKs and deadlocks
"Philippe Lang" <[EMAIL PROTECTED]> writes:
> I got a deadlock i
"Philippe Lang" <[EMAIL PROTECTED]> writes:
> I got a deadlock in my database this morning.
There is no deadlock here. The ungranted rows in pg_locks all point to
the transaction ID 6489299, which belongs to PID 11346, which is this
one:
> 11346 ?? R236:43.23 postmaster: jlroubaty groupefp
--
De : Stephan Szabo [mailto:[EMAIL PROTECTED]
Envoyé : vendredi, 22. octobre 2004 15:30
À : Philippe Lang
Cc : [EMAIL PROTECTED]
Objet : Re: [GENERAL] FKs and deadlocks
On Fri, 22 Oct 2004, Philippe Lang wrote:
> I have tried to correct that by adding a "SET CONSTRAINTS ALL DEFERRED&qu
Stephan Szabo <[EMAIL PROTECTED]> writes:
> On Fri, 22 Oct 2004, Philippe Lang wrote:
>> I don't know if anyone has a better idea, but I would like to try taking
>> away some FKs in my schema. My problem is that I really don't know which
>> one to delete. There are over 40 tables. Are there rules t
On Fri, 22 Oct 2004, Philippe Lang wrote:
> I have tried to correct that by adding a "SET CONSTRAINTS ALL DEFERRED"
> in every trigger and function, hoping it would solve my problem. Maybe
> it helped, but it did not solve anything.
Note that set constraints all deferred does nothing unless you m
Hello,
As the amount of simultaneous users of my database grows (25 users
sometimes, PGSQL 7.4.5), deadlocks are unfortunately more and more
frequent. I guess this is due to the FKs problem with Postgresql.
I have tried to correct that by adding a "SET CONSTRAINTS ALL DEFERRED"
in every trigger a
