Received: from meryl.it.uu.se (root@meryl.it.uu.se [130.238.12.42]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA99900; Tue, 25 Jan 2000 05:30:41 -0500 (EST) (envelope-from e99re41@DoCS.UU.SE) Received: from Val.DoCS.UU.SE (e99re41@Val.DoCS.UU.SE [130.238.9.94]) by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id LAA23593; Tue, 25 Jan 2000 11:30:33 +0100 (MET) Received: from localhost (e99re41@localhost) by Val.DoCS.UU.SE (8.6.12/8.6.12) with SMTP id LAA11954; Tue, 25 Jan 2000 11:30:31 +0100 X-Authentication-Warning: Val.DoCS.UU.SE: e99re41 owned process doing -bs Date: Tue, 25 Jan 2000 11:30:30 +0100 (MET) From: Peter Eisentraut Reply-To: Peter Eisentraut To: Bruce Momjian cc: Tom Lane , Chris Bitmead , pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org Subject: Re: [SQL] Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace In-Reply-To: <200001250355.WAA23883@candle.pha.pa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 24 Jan 2000, Bruce Momjian wrote: > > In short, it's not clear to me that supporting DISTINCT ON is a good use > > of our limited resources. I'm willing to pull it out, but not to fix it. > > Does someone else want to take responsibility for it? > > OK, we can disable it and put it on the TODO list. It is already there. > Am I wrong or can DISTINCT ON not be rewritten in terms of GROUP BY in all cases? -- Peter Eisentraut Sernanders vaeg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden