Re: Planning aggregates which require sorted or distinct

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gavin Sherry <swm(at)alcove(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Planning aggregates which require sorted or distinct
Date: 2007-01-20 04:40:35
Message-ID: 9302.1169268035@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gavin Sherry <swm(at)alcove(dot)com(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Sherry 2007-01-20 04:58:00 Re: Planning aggregates which require sorted or distinct
Previous Message Tom Lane 2007-01-20 04:33:11 Re: savepoint improvements