Re: Planning aggregates which require sorted or distinct - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Planning aggregates which require sorted or distinct
Date
Msg-id 9302.1169268035@sss.pgh.pa.us
Whole thread Raw
In response to Re: Planning aggregates which require sorted or distinct  (Gavin Sherry <swm@alcove.com.au>)
Responses Re: Planning aggregates which require sorted or distinct
List pgsql-hackers
Gavin Sherry <swm@alcove.com.au> writes:
> On Fri, 19 Jan 2007, Tom Lane wrote:
>> Er, what primary key would that be exactly?  And even if you had a key,
>> I wouldn't call joining on it trivial; I'd call it expensive ...

> I should have used slightly different language. What I meant to say was,
> both sets are primarily sorted by saledate so they can be merged back
> together. This is why I said it was trivial.

Ah, my misunderstanding.  Then isn't this basically isomorphic to what
I was thinking of, ie, somewhat-smarter Aggref nodes attached to the
existing GroupAggregate plan node?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: savepoint improvements
Next
From: Gavin Sherry
Date:
Subject: Re: Planning aggregates which require sorted or distinct