| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Nimesh Satam <nimesh(dot)zedo(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, nimesh(at)zedo(dot)com |
| Subject: | Re: Append Cost in query planners |
| Date: | 2007-10-29 15:22:07 |
| Message-ID: | 4725FA9F.7050207@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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 parameters should we consider while opting for
> partition?
Whether it helps or not depends on many things, like the distribution of
the data, but it's worth trying. I'd try that first, before worrying
about config parameters.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Campbell, Lance | 2007-10-29 16:33:57 | Re: Suggestions on an update query |
| Previous Message | Gregory Stark | 2007-10-29 13:40:39 | Re: partitioned table and ORDER BY indexed_field DESC LIMIT 1 |