Re: How is this possible? (more on deadlocks)

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Carlos Moreno <moreno(at)mochima(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How is this possible? (more on deadlocks)
Date: 2004-08-24 21:26:57
Message-ID: 20040824142502.O59661@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Tue, 24 Aug 2004, Carlos Moreno wrote:

> Ok, now I'm really intrigued by what looks to me
> (possibly from a naive point of view) like a bug,
> or rather, a limitation on the implementation.

Yep. See recent (and historical) discussions on
needing a weaker lock than FOR UPDATE for handling
foreign keys.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-08-24 21:30:56 Re: NAB : insert into <table> select distinct <fields> => when used on null, distinct causes loss of type knowledge
Previous Message Frank van Vugt 2004-08-24 21:16:37 NAB : insert into <table> select distinct <fields> => when used on null, distinct causes loss of type knowledge