From: | hyelluas <helen_yelluas(at)mcafee(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: constraint partition issue |
Date: | 2011-03-23 17:10:50 |
Message-ID: | 1300900250732-4259142.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
sorry, my table has many columns and missed the datex when make it look
smaller.
datex is the column in the table. This is the driving constraint.
My task is to have 30 days of data with 5mln to 10 mln rec in 1 hour table,
so I partition it by hour table and combine them into days, which are
combined into month total table. My query will have " where datex between a
and b" , for 2-5 days ,across the "day" boundaries , so that partition
exclusion is so much important.
I don't undertsand why the optimizer goes to the children when it hits the
constraint on the parent that shows the date range on that parent ?
thank you.
Helen
--
View this message in context: http://postgresql.1045698.n5.nabble.com/constraint-partition-issue-tp4258004p4259142.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Jens Kapp | 2011-03-23 17:14:27 | Re: Recursive function that receives a list of IDs and returns all child IDs |
Previous Message | Adrian Klaver | 2011-03-23 17:03:23 | Re: pg_dump problems |