Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id A861F63325A for ; Tue, 27 Apr 2010 19:15:03 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 36119-01 for ; Tue, 27 Apr 2010 22:14:54 +0000 (UTC) X-Greylist: delayed 00:10:16.342424 by SQLgrey-1.7.6 Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by mail.postgresql.org (Postfix) with ESMTP id AD49563322B for ; Tue, 27 Apr 2010 19:14:55 -0300 (ADT) Received: from ms6.yyz2.afilias-ops.info ([10.50.129.112] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from ) id 1O6stP-0004bC-7c; Tue, 27 Apr 2010 22:04:35 +0000 Received: from tor-gateway.afilias.info ([199.15.87.4] helo=[10.10.46.23]) by smtp.afilias.info with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1O6stP-0004pN-79; Tue, 27 Apr 2010 22:04:35 +0000 Message-ID: <4BD75F6B.1020202@ca.afilias.info> Date: Tue, 27 Apr 2010 18:04:27 -0400 From: Steve Singer User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Josh Berkus CC: Matthew Bellew , pgsql-testers@postgresql.org Subject: Re: schema.table.column syntax no longer supported? References: <4BC7A517.4010507@agliodbs.com> In-Reply-To: <4BC7A517.4010507@agliodbs.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.21 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201004/12 X-Sequence-Number: 82 Josh Berkus wrote: >> This was hit while trying to install a server (www.labkey.org). The >> install scripts had dozens of failures of this type under 9.0Alpha4. >> INSERT,UPDATE,DELETE had variations on this error message. > > Thanks, will see if I can replicate. > I can replicate this as well with a recent cvs/git build. CREATE TABLE a(a int4); CREATE TABLE b(b int4); UPDATE public.a SET a=1 FROM public.b WHERE public.a.a=public.b.b; will replicate this issue It works fine in 8.4 -- Steve Singer Afilias Canada Data Services Developer 416-673-1142