Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA60644; Tue, 29 Feb 2000 10:57:05 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id JAA28930; Tue, 29 Feb 2000 09:57:56 -0500 (EST) To: Thomas Lockhart cc: Bruce Momjian , "'pgsql-sql@postgresql.org'" , PostgreSQL Development Subject: Re: [HACKERS] Re: [SQL] prob with aggregate and group by - returns multiplesh In-reply-to: <38BB6BA6.B5FACCAD@alumni.caltech.edu> References: <200002290559.AAA10605@candle.pha.pa.us> <38BB6BA6.B5FACCAD@alumni.caltech.edu> Comments: In-reply-to Thomas Lockhart message dated "Tue, 29 Feb 2000 06:48:06 +0000" Date: Tue, 29 Feb 2000 09:57:56 -0500 Message-ID: <28927.951836276@sss.pgh.pa.us> From: Tom Lane >>>> If not, I'd vote for pulling it out. That's a heck of a poor word to >>>> reserve. >> I am afraid of lots of user complaints, even if we had not already used >> TEMP. > OK, but we've already got "user complaints" about TEMP being a > reserved word, so that part seems to balance out. There is apparently > no basis in published standards for TEMP being a reserved word. And > btw it is not currently documented as a reserved word in > syntax.sgml... The real problem is not that we accept TEMP as a synonym for TEMPORARY; it is that we treat TEMP as a reserved word. What are the chances that we could make it a member of the ColId list? I am thinking that "... INTO TEMP temp" is *not* ambiguous given one token lookahead... regards, tom lane