Re: FOR KEY LOCK foreign keys

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Joel Jacobson <joel(at)gluefinance(dot)com>
Subject: Re: FOR KEY LOCK foreign keys
Date: 2011-01-14 18:08:27
Message-ID: AANLkTi=+=5fqPRaWa_YKrQA3BYKmZubfPoL7Mbb=W9+4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 14, 2011 at 1:00 PM, David E. Wheeler <david(at)kineticode(dot)com> wrote:
> On Jan 13, 2011, at 1:58 PM, Alvaro Herrera wrote:
>
>> Something else that might be of interest: the patch as presented here
>> does NOT solve the deadlock problem originally presented by Joel
>> Jacobson.  It does solve the second, simpler example I presented in my
>> blog article referenced above, however.  I need to have a closer look at
>> that problem to figure out if we could fix the deadlock too.
>
> Sounds like a big win already. Should this be considered a WIP patch, though, if you still plan to look at Joel's deadlock example?

Alvaro, are you planning to add this to the CF?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-01-14 18:09:11 Re: Re: [COMMITTERS] pgsql: Exit from base backups when shutdown is requested
Previous Message Robert Haas 2011-01-14 18:07:55 Re: limiting hint bit I/O