From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | David E(dot) Wheeler <david(at)kineticode(dot)com> |
Cc: | 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:14:18 |
Message-ID: | 1295028828-sup-2187@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from David E. Wheeler's message of vie ene 14 15:00:48 -0300 2011:
> 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?
Not necessarily -- we can implement that as a later refinement/improvement.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-01-14 18:14:27 | Re: FOR KEY LOCK foreign keys |
Previous Message | Robert Haas | 2011-01-14 18:14:02 | Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements. |