public inbox for [email protected]  

help / color / mirror / Atom feed

From: Michael Paesold <[email protected]>
To: Tom Lane <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: [email protected]
Subject: Re: FOR SHARE vs FOR UPDATE locks
Date: Fri, 01 Dec 2006 08:16:41 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Tom Lane wrote:
 > I'm tempted to just error out in this scenario rather than allow the
 > lock upgrade.  Thoughts?

Although this seems to be a technically hard problem, the above sentence 
does not sound like the PostgreSQL way to solve problems (rather like 
MySQL). ;-)

Now seriously, isn't this a perfectly feasible scenario? E.g. the outer 
transaction acquires a shared lock because of foreign key constraints, and 
the sub transaction later wants to update that row?

Best Regards
Michael Paesold

view thread (32+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: FOR SHARE vs FOR UPDATE locks
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox