Re: Locking when concurrent updated of foreign references

From: Jesper Krogh <jesper(at)krogh(dot)cc>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Locking when concurrent updated of foreign references
Date: 2011-04-11 20:07:33
Message-ID: 4DA35F85.9050100@krogh.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-04-11 20:13:52 Re: lowering privs in SECURITY DEFINER function
Previous Message Tom Lane 2011-04-11 19:44:12 fn_collation in FmgrInfo considered harmful