Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id ABEC9B5DBC4 for ; Tue, 14 Jun 2011 22:07:10 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 20207-04 for ; Wed, 15 Jun 2011 01:07:04 +0000 (UTC) Received: from news.hub.org (news.hub.org [200.46.204.72]) by mail.postgresql.org (Postfix) with ESMTP id 7DE51B5DBD3 for ; Tue, 14 Jun 2011 22:07:04 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.14.4/8.14.4) with ESMTP id p5F173hB024951 for ; Tue, 14 Jun 2011 22:07:03 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.14.4/8.14.4/Submit) id p5F11pKs018505 for pgsql-sql@postgresql.org; Tue, 14 Jun 2011 22:01:51 -0300 (ADT) (envelope-from news) From: "greg.fenton" X-Newsgroups: pgsql.sql Subject: Re: Select For Update and Left Outer Join Date: Tue, 14 Jun 2011 18:01:51 -0700 (PDT) Organization: http://groups.google.com Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Complaints-To: groups-abuse@google.com Complaints-To: groups-abuse@google.com Injection-Info: v10g2000yqn.googlegroups.com; posting-host=38.99.165.166; posting-account=PjwI3woAAAAxlLr6lAHwQkUIJey-u-qo User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HNKRUAELSC X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 5.2; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24,gzip(gfe) To: pgsql-sql@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, T_RP_MATCHES_RCVD=-0.01, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201106/49 X-Sequence-Number: 35515 On Apr 28, 2:00=A0am, pate...@patearl.net (Patrick Earl) wrote: > This is a follow-up to an old message by Tom Lane: > > =A0 =A0http://archives.postgresql.org/pgsql-sql/2006-10/msg00080.php > [...] > > select * from Pet > left join Dog on Dog.Id =3D Pet.Id > left join Cat on Cat.Id =3D Pet.Id > > Now suppose you want to lock to ensure that your Cat is not updated > concurrently. =A0You 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)