Skip site navigation (1) Skip section navigation (2)

Re: FOR KEY LOCK foreign keys

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FOR KEY LOCK foreign keys
Date: 2011-08-03 17:03:49
Message-ID: 1312390939-sup-3097@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Excerpts from Robert Haas's message of mié ago 03 12:14:15 -0400 2011:
> On Wed, Jul 27, 2011 at 7:16 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
> > One thing I have not addressed is Noah's idea about creating a new lock
> > mode, KEY UPDATE, that would let us solve the initial problem that this
> > patch set to resolve in the first place.  I am not clear on exactly how
> > that is to be implemented, because currently heap_update and heap_delete
> > do not grab any kind of lock but instead do their own ad-hoc waiting.  I
> > think that might need to be reshuffled a bit, to which I haven't gotten
> > yet, and is a radical enough idea that I would like it to be discussed
> > by the hackers community at large before setting sail on developing it.
> > In the meantime, this patch does improve the current situation quite a
> > lot.
> 
> I haven't looked at the patch yet, but do you have a pointer to Noah's
> proposal?  And/or a description of how it differs from what you
> implemented here?

Yes, see his review email here:
  http://archives.postgresql.org/message-id/20110211071322.GB26971@tornado.leadboat.com

It's long, but search for the part where he talks about "KEY UPDATE".
The way my patch works is explained by Noah there.

-- 
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2011-08-03 17:07:22
Subject: Re: Transient plans versus the SPI API
Previous:From: Kevin GrittnerDate: 2011-08-03 17:01:27
Subject: Re: WIP fix proposal for bug #6123

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group