Nimesh Satam wrote:
> Thanks for the information. join_collapse_limit = 1 is already set before
> sending the query plan.
I assume that was a typo, and you really set it to 10 or higher...
> Will a index scan on metrics.netkey help in improving the performance what
> other configuration parameter
Heikki,
Thanks for the information. join_collapse_limit = 1 is already set before
sending the query plan.
Will a index scan on metrics.netkey help in improving the performance what
other configuration parameters should we consider while opting for
partition?
Regards,
Nimesh.
On 10/29/07, Heik
Nimesh Satam wrote:
> Heikki,
>
>
> Thanks for your reply. Will try to do the changes and rivert back. I had one
> more requirement for partitioning.
>
> I wanted to inherit two different tables for partition. Below is the query
> used to create the table, an crete the inheritance.
>
>
> CREAT
Heikki,
Thanks for your reply. Will try to do the changes and rivert back. I had one
more requirement for partitioning.
I wanted to inherit two different tables for partition. Below is the query
used to create the table, an crete the inheritance.
CREATE TABLE metrics_d20070601 (CHECK (sqldate
Nimesh Satam wrote:
> Following is the full plan of the query using partition. Let me know if you
> need any further information.
What indexes are there on the table partitions? You didn't post the
query, but it looks like your doing a join between rpt_network and the
partitioned table. An index o
Nimesh Satam wrote:
> We are trying to implement partition on one tables on date basis. the
> overall cost and timming and cost of the query is increasing on the Append
> of the child table output. As shown below:
>
> *-> Append (cost=0.00..112217.92 rows=2752906 width=52) (actual time=
> 2454.2