Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3DFBX850092 for ; Fri, 13 Apr 2001 11:11:33 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f3DFBQR03807; Fri, 13 Apr 2001 11:11:26 -0400 (EDT) To: Tim Perdue cc: pgsql-sql@postgresql.org Subject: Re: Full outer join In-reply-to: <20010413082322.W446@mail.perdue.net> References: <20010412130950.O446@mail.perdue.net> <3104.987145352@sss.pgh.pa.us> <20010413082322.W446@mail.perdue.net> Comments: In-reply-to Tim Perdue message dated "Fri, 13 Apr 2001 08:23:22 -0500" Date: Fri, 13 Apr 2001 11:11:26 -0400 Message-ID: <3804.987174686@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/196 X-Sequence-Number: 2546 Tim Perdue writes: > Does it still work with those revised CREATE statements? Yes, works fine here. >> What version are you using? > That's RC3 and RC1. Curious. I'd expect this to happen for column datatypes whose '=' operator isn't marked mergejoinable, but plain old int certainly doesn't have that problem. I think there's something you haven't told us. Is either of these tables actually a view? regards, tom lane