Received: from mail.ngi.de ([195.243.0.227]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA97342 for ; Tue, 25 Jan 2000 05:11:59 -0500 (EST) (envelope-from michael@fam-meskes.de) Received: from p3E9B988E.dip0.t-ipconnect.de (root@p3E9B988E.dip0.t-ipconnect.de [62.155.152.142]) by mail.ngi.de (8.9.3/8.9.3) with ESMTP id LAA78883 for ; Tue, 25 Jan 2000 11:12:52 +0100 (CET) Received: (from michael@localhost) by tanja.fam-meskes.de (8.9.3/8.9.3/Debian 8.9.3-6) id IAA01782 for pgsql-hackers@postgresql.org; Tue, 25 Jan 2000 08:12:36 +0100 Date: Tue, 25 Jan 2000 08:12:36 +0100 From: Michael Meskes To: pgsql-hackers@postgresql.org Subject: Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace Message-ID: <20000125081236.A1774@fam-meskes.de> Mail-Followup-To: pgsql-hackers@postgresql.org References: <11547.948771949@sss.pgh.pa.us> <200001250355.WAA23883@candle.pha.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In-Reply-To: <200001250355.WAA23883@candle.pha.pa.us>; from pgman@candle.pha.pa.us on Mon, Jan 24, 2000 at 10:55:02PM -0500 On Mon, Jan 24, 2000 at 10:55:02PM -0500, 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. Or, as you suggested earlier, throw a NOTICE instead of disabling it. But then I doubt Tom talked about physically removing the code anyway. Disabling certainly is enough. Michael -- Michael Meskes | Go SF 49ers! Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire! Tel.: (+49) 2431/72651 | Use Debian GNU/Linux! Email: Michael@Fam-Meskes.De | Use PostgreSQL!