X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id B006BD1B506 for ; Fri, 10 Oct 2003 04:50:20 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 22647-10 for ; Fri, 10 Oct 2003 01:49:35 -0300 (ADT) Received: from smtp.istop.com (dci.doncaster.on.ca [66.11.168.194]) by svr1.postgresql.org (Postfix) with ESMTP id 4A782D1B545 for ; Fri, 10 Oct 2003 01:49:34 -0300 (ADT) Received: from stark.dyndns.tv (gsstark.mtl.istop.com [66.11.160.162]) by smtp.istop.com (Postfix) with ESMTP id C3F8536983; Fri, 10 Oct 2003 00:49:27 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=stark.dyndns.tv ident=foobar) by stark.dyndns.tv with smtp (Exim 3.36 #1 (Debian)) id 1A7pDT-0005Xi-00; Fri, 10 Oct 2003 00:49:27 -0400 To: Dror Matalon Cc: Postgresql Performance Subject: Re: Speeding up Aggregates References: <20031003202120.GO87525@rlx11.zapatec.com> <1065217488.91586.3.camel@jester> <20031003215347.GQ87525@rlx11.zapatec.com> <1065219028.91586.8.camel@jester> <87llrvbx0f.fsf@stark.dyndns.tv> <20031008181819.GJ2979@rlx11.zapatec.com> <87ekxm9fjf.fsf@stark.dyndns.tv> <20031010004446.GN2979@rlx11.zapatec.com> <20031010013522.GB18596@wolff.to> <20031010035526.GT2979@rlx11.zapatec.com> In-Reply-To: <20031010035526.GT2979@rlx11.zapatec.com> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 10 Oct 2003 00:49:27 -0400 Message-ID: <874qyh8zoo.fsf@stark.dyndns.tv> Lines: 28 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/321 X-Sequence-Number: 4069 Dror Matalon writes: > Ouch. I just double checked and you're right. Is this considered a bug, > or just an implementation issue? Call it a wishlist bug. The problem is it would be a hard feature to implement properly. And none of the people paid to work on postgres by various companies seem to have this on their to-do lists. So don't expect it in the near future. > While I've seen this hint a few times in the lists, it seems like it's > one of those magic incantations that those in the know, know about, and > that people new to postgres are going to be surprised by the need to use > this idiom. Yup. Though it's in the FAQ and comes up on the mailing list about once a week or so, so it's hard to see how to document it any better. Perhaps a warning specifically on the min/max functions in the documentation? Say, what do people think about a comment board thing like php.net has attached to the documentation. People can add comments that show up directly on the bottom of the documentation for each function. I find it's mostly full of junk but skimming the comments often turns up one or two relevant warnings, especially when I'm wondering why something's not behaving the way I expect. -- greg