Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Re: Improving planner's handling of min/max aggregate optimization
On Mon, Nov 1, 2010 at 8:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: > This will make the min/max optimization code more visible to the rest of > the planner in a couple of ways: aside from being called at two places > not one, it will have some intermediate state that'll have to be kept in > PlannerInfo, and the "useful pathkeys" logic will have to be complicit > in letting paths that match the aggregates' requirements survive. But > it's not real bad, and it seems a lot better than continuing with the > fully-at-arms-length approach. > > Comments? +1. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
In response to
- Improving planner's handling of min/max aggregate optimization at 2010-11-02 03:16:31 from Tom Lane
pgsql-hackers by date
Next: From: Kevin Grittner Date: 2010-11-03 19:28:03 Subject: Re: max_wal_senders must die Previous: From: Alvaro Herrera Date: 2010-11-03 17:15:39 Subject: Fwd: Re: ALTER OBJECT any_name SET SCHEMA name