Re: [PERFORM] Partitioned tables in queries

2006-07-25 Thread Andrew Hammond
> 2. I found that using the now() function - and arbitrary interval will > produce a different execution plan that using a specific date. For example: > assuming the current time is 16:00: > a) where start_date > now() - interval '4 hours' scans all child tables. > b) where start_date >

Re: [PERFORM] Partitioned tables in queries

2006-07-21 Thread Kevin Keith
My post might have been a little premature - and I apologize for that. I have figured out what was causing the problem: 1. Constraint exclusion was disabled. I re-enabled. 2. I found that using the now() function - and arbitrary interval will produce a different execution plan that using a speci

Re: [PERFORM] Partitioned tables in queries

2006-07-21 Thread Steve Atkins
On Jul 21, 2006, at 12:17 PM, Kevin Keith wrote: I have a case where I am partitioning tables based on a date range in version 8.1.4. For example: table_with_millions_of_records interaction_id char(16) primary key start_date timestamp (without timezone) - indexed .. other columns child_1

[PERFORM] Partitioned tables in queries

2006-07-21 Thread Kevin Keith
I have a case where I am partitioning tables based on a date range in version 8.1.4. For example: table_with_millions_of_records interaction_id char(16) primary key start_date timestamp (without timezone) - indexed .. other columns child_1 start_date >= 2006-07-21 00:00:00 child_2 start_