| From: | Jochen Erwied <jochen(at)pgsql-performance(dot)erwied(dot)eu> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: dates and partitioning |
| Date: | 2010-07-20 15:55:48 |
| Message-ID: | 928016768.20100720175548@erwied.eu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Tuesday, July 20, 2010, 5:36:07 PM you wrote:
> 2) the above query creates a plan that does a sequential scan & filter on
> every partition. Why won't it only hit the correct partitions? Is it due to
> the way the date was specified? or maybe the "at time zone" syntax?
Quick guess: How is your 'constraint_exclusion'-setting?
Which version of postgres?
--
Jochen Erwied | home: jochen(at)erwied(dot)eu +49-208-38800-18, FAX: -19
Sauerbruchstr. 17 | work: joe(at)mbs-software(dot)de +49-2151-7294-24, FAX: -50
D-45470 Muelheim | mobile: jochen(dot)erwied(at)vodafone(dot)de +49-173-5404164
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kneringer, Armin | 2010-07-20 16:25:55 | potential performance gain by query planner optimization |
| Previous Message | Brad Nicholson | 2010-07-20 15:55:30 | Re: dates and partitioning |