Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA64201 for ; Thu, 5 Aug 1999 12:30:29 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id MAA04928; Thu, 5 Aug 1999 12:29:34 -0400 (EDT) To: "Ross J. Reedstrom" cc: rob caSSon , pgsql-sql@postgresql.org Subject: Re: [SQL] primary key view failure In-reply-to: Your message of Thu, 5 Aug 1999 11:09:08 -0500 <19990805110908.C7495@wallace.ece.rice.edu> Date: Thu, 05 Aug 1999 12:29:34 -0400 Message-ID: <4926.933870574@sss.pgh.pa.us> From: Tom Lane "Ross J. Reedstrom" writes: > On Thu, Aug 05, 1999 at 10:26:16AM -0400, Tom Lane wrote: >> rob caSSon writes: >>>> i have a perfectly valid sql statement that returns expected results, but >>>> when i create a view based on the same sql, i get 0. >> >> Your example seems to work fine for me with current sources. >> What version are you running? > I just got the same results as Rob, with a 6.5.0 install, OK, I went back and tried it with 6.5.1 and indeed see the same failure as Rob. So it's something that's been fixed in the current sources. I dunno what --- but I did a *lot* of work on the parser's array support last month, and that might have something to do with it... > and a hopefully helpful error message: > idas_proto=> \d blah > ERROR: get_ruledef of blah: unknown node type 111 in check_if_rte_used() That one is still there in current sources. Will clean it up. > So, is this fixed in 6.5.1, or is it something that needs backporting from > current? A backport from current may not be too practical, unless someone wants to try to identify exactly what's failing in 6.5.*. I bet it's an array issue, but beyond that I'm clueless. regards, tom lane