| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | David E(dot) Wheeler <david(at)kineticode(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:14:27 |
| Message-ID: | 1295028859-sup-6640@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Robert Haas's message of vie ene 14 15:08:27 -0300 2011:
> 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?
Eh, yes.
--
Á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 | Tom Lane | 2011-01-14 18:16:45 | Re: limiting hint bit I/O |
| Previous Message | Alvaro Herrera | 2011-01-14 18:14:18 | Re: FOR KEY LOCK foreign keys |