Received: from golem.jpl.nasa.gov (root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.8.8/8.7.5) with ESMTP id JAA26120 for ; Thu, 10 Sep 1998 09:38:28 -0400 (EDT) Received: from alumni.caltech.edu (localhost [127.0.0.1]) by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id NAA23761; Thu, 10 Sep 1998 13:38:14 GMT Sender: tgl@mythos.jpl.nasa.gov Message-ID: <35F7D645.FE548C57@alumni.caltech.edu> Date: Thu, 10 Sep 1998 13:38:13 +0000 From: "Thomas G. Lockhart" Organization: Caltech/JPL X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.30 i686) MIME-Version: 1.0 To: Bruce Momjian CC: hackers@postgreSQL.org Subject: Re: [HACKERS] open 6.4 items References: <199809100615.CAA24253@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > > remove PARSEDEBUG defines if not longer needed > > OK. You really want those gone, don't you! > I can move it to the TODO list, OK? :-) No, leave it on the v6.4 FixIt list. This is the start of that list, right? > > > SELECT oid @ oid @ oid FROM pg_user fails with parser error, not > > > function error > Should I move this to the TODO list now? Well, I don't know how you would fix it without rewriting the parser or changing the associativity of generic operators. I would suggest leaving it off the ToDo list altogether, unless someone can suggest a viable solution. The example suggests it is a problem with OIDs or with the "@" operator, not a fundamental feature of the yacc/bison parser. > > > no min/max for oid type > I can move some of the items off now, rather than wait until just > before 6.4 to be released to move them. OK? Yeah. Let's turn this list into the v6.4 FixIt list; you've done one for every release I can remember and it has been very helpful. Be sure to add the views problem to this list ;) Also, add the html/hardcopy documentation since we will re-release the User's Guide, Admin Guide, and Programmer's Guide. - Tom