From: greg.fenton <greg.fenton@gmail.com>
To: pgsql-sql@postgresql.org
Subject: Re: Select For Update and Left Outer Join
Date: Tue, 14 Jun 2011 18:01:51 -0700 (PDT)
Message-ID: <f86b2eee-8b66-44ea-955e-76e618434024@v10g2000yqn.googlegroups.com> (raw)
References: <BANLkTi=xdjap-wiMhUm7=MgmWXm77DNNng@mail.gmail.com>
On Apr 28, 2:00 am, pate...@patearl.net (Patrick Earl) wrote:
> This is a follow-up to an old message by Tom Lane:
>
> http://archives.postgresql.org/pgsql-sql/2006-10/msg00080.php
>
[...]
>
> select * from Pet
> left join Dog on Dog.Id = Pet.Id
> left join Cat on Cat.Id = Pet.Id
>
> Now suppose you want to lock to ensure that your Cat is not updated
> concurrently. You add FOR UPDATE, but then PostgreSQL gets upset and
> complains that locking on the nullable side of an outer join is not
> allowed.
>
Any resolve to or update on this issue?
Thanks,
greg.fenton
--
greg dot fenton at gmail (yes, dot com)
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: pgsql-sql@postgresql.org
Cc: greg.fenton@gmail.com
Subject: Re: Select For Update and Left Outer Join
In-Reply-To: <f86b2eee-8b66-44ea-955e-76e618434024@v10g2000yqn.googlegroups.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox