Re: Locking when concurrent updated of foreign references - Mailing list pgsql-hackers

From Jesper Krogh
Subject Re: Locking when concurrent updated of foreign references
Date
Msg-id 4DA35F85.9050100@krogh.cc
Whole thread Raw
In response to Locking when concurrent updated of foreign references  (Jesper Krogh <jesper@krogh.cc>)
Responses Re: Locking when concurrent updated of foreign references  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On 2011-04-11 20:18, Jesper Krogh wrote:
> Hi.
>
> This seem a bit strange to me. In short:
Not any more I.. I guess what made me a bit confused was that
a "update table set key = value" would acually block out changes
on tables referencing this tuple even if the referenced column wasn't
effected by the update.

But when the locking is done "row-level" then it is correct
to do it that way. It would allthough be nice with a weaker
locklevel for that kind of updates (I have no clue if that is
a hard problem).

-- 
Jesper


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: fn_collation in FmgrInfo considered harmful
Next
From: Alvaro Herrera
Date:
Subject: Re: lowering privs in SECURITY DEFINER function