Re: Aggregates with non-commutative transition functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Emmanuel Charpentier <charpent(at)bacbuc(dot)dyndns(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Aggregates with non-commutative transition functions
Date: 2003-02-16 19:36:09
Message-ID: 28591.1045424169@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Emmanuel Charpentier <charpent(at)bacbuc(dot)dyndns(dot)org> writes:
> Tom Lane wrote:
>> Note the lack of an extra sort above the subquery. This provides a
>> general technique for controlling the ordering of inputs to a
>> user-written aggregate function, even when grouping.

> Schn ! I suppose that this has other fringe benefits for planning in
> general ...

Yes, it should save cycles in many scenarios, so I thought it was worth
doing in any case.

> Do you plan incorporation in some forthcoming 7.3.x ? Or push it back
> to 7.4 ?

No, I would not risk back-patching this into 7.3.*. It's not a bug fix.

(But having said that, you could get the diffs from the CVS server and
back-patch to create your own private 7.3 variant, if you can't wait
for 7.4. Offhand I do not think there'd be any great difficulty in
applying the change to 7.3 branch.)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dima Tkach 2003-02-16 20:37:17 Re: Index not used with IS NULL
Previous Message Tom Lane 2003-02-16 19:29:13 Re: In 7.3.1, will I be able to reindex toast?