On 4/12/2013 12:10 PM, fburg...@radiantblue.com wrote:
The SQL query should be: select count(*) from dna_strands where cid = 1;
ah. I suspected as much.its so hard to analyze problems with
incorrect information and so easy to make wrong assumptions.
I just realize don't think this is n
Hi John,
The SQL query should be: select count(*) from dna_strands where cid = 1;
I just realize don't think this is not going to work. if for the sake of argument that cid = 1 is much more likely be be found in a more recent partition, any inverse search mechanism in the planner will find tha
On 4/12/2013 11:46 AM, fburg...@radiantblue.com wrote:
We are having performance related problems on one of our big data
Partition tables. The table is partitioned by date and the partitions
are organized from Jan 2003 thru Dec 2013.
We have 268 child partitions associated with the Parent table,
Sorry, Is this visible?
We are having performance related problems on one of our big data Partition tables. The table is partitioned by date and the partitions are organized from Jan 2003 thru Dec 2013. We have 268 child partitions associated with the Parent table, and we have constraint_exclusi
We are having performance related problems on one of our big data Partition tables. The table is partitioned by date and the partitions are organized from Jan 2003 thru Dec 2013. We have 268 child partitions associated with the Parent table, and we have constraint_exclusion=partition set.
The ex
