pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Dror Matalon <dror@zapatec.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Speeding up Aggregates
Date: 10 Oct 2003 00:49:27 -0400
Message-ID: <874qyh8zoo.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <20031010035526.GT2979@rlx11.zapatec.com>
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>


Dror Matalon <dror@zapatec.com> 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




view thread (22+ messages)  latest in thread

Message-ID: <874qyh8zoo.fsf@stark.dyndns.tv>
Permalink:  ../874qyh8zoo.fsf@stark.dyndns.tv/
Also on:    postgresql.org/message-id/874qyh8zoo.fsf@stark.dyndns.tv

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: gsstark@mit.edu, dror@zapatec.com
  Subject: Re: Speeding up Aggregates
  In-Reply-To: <874qyh8zoo.fsf@stark.dyndns.tv>
  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> <874qyh8zoo.fsf@stark.dyndns.tv>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox