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

From Gavin Sherry
Subject Re: Planning aggregates which require sorted or distinct
Date
Msg-id Pine.LNX.4.58.0701210056380.30027@linuxworld.com.au
Whole thread Raw
In response to Re: Planning aggregates which require sorted or distinct  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
On Sat, 20 Jan 2007, Gregory Stark wrote:

> However for RANGE UNBOUNDED PRECEDING we can apply a different plan. Keep the
> state variable for each window aggregate around for the entire time. For each
> record apply the state transition function then apply the FINAL function to
> generate the result for that record but keep the state variable as it was for
> the next record.

Yes, I made reference to this case else where in the email (or was it a
different email in the thread?).

Thanks,

Gavin



pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Planning aggregates which require sorted or distinct
Next
From: "Simon Riggs"
Date:
Subject: Re: Planning aggregates which require sorted or distinct