Re: Deadlock situation using foreign keys (reproduceable)

From: "Mario Weilguni" <mario(dot)weilguni(at)icomedias(dot)com>
To: "Stephan Szabo" <sszabo(at)megazone23(dot)bigpanda(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Deadlock situation using foreign keys (reproduceable)
Date: 2002-08-26 15:30:28
Message-ID: 4D618F6493CE064A844A5D496733D667038FDC@freedom.icomedias.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Not a lower strength lock, I would, but I'm not so familiar with the postgres
internals. I modified ri-triggers.c to exclude certain tables from the
locking itself (because I know the tables are not updated).

-----Ursprüngliche Nachricht-----
Von: Stephan Szabo [mailto:sszabo(at)megazone23(dot)bigpanda(dot)com]
Gesendet: Montag, 26. August 2002 17:29
An: Mario Weilguni
Cc: pgsql-hackers(at)postgresql(dot)org
Betreff: Re: [HACKERS] Deadlock situation using foreign keys
(reproduceable)

On Mon, 26 Aug 2002, Mario Weilguni wrote:

> I wrote this patch for my system, and it works fine. However, it's a
> really ugly workaround. I can publish the source if anybody is
> interested.

Which, the for update one or a lower strength lock? In either case,
certainly.

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sir Mordred The Traitor 2002-08-26 15:31:26 Re: @(#)Mordred Labs advisory 0x0007: Remove DoS in PostgreSQL
Previous Message Stephan Szabo 2002-08-26 15:29:09 Re: Deadlock situation using foreign keys (reproduceable)