From: | "greg(dot)fenton" <greg(dot)fenton(at)gmail(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Select For Update and Left Outer Join |
Date: | 2011-06-15 01:01:51 |
Message-ID: | f86b2eee-8b66-44ea-955e-76e618434024@v10g2000yqn.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Apr 28, 2:00 am, pate(dot)(dot)(dot)(at)patearl(dot)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)
From | Date | Subject | |
---|---|---|---|
Next Message | Jira, Marcel | 2011-06-15 15:23:15 | Merge overlapping time-periods |
Previous Message | Amitabh Kant | 2011-06-14 20:14:25 | Re: Storage of Indian Language text in postgresql through PHP |