Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Append Cost in query planners
- 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: Mon, 29 Oct 2007 15:22:07 +0000
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
- References:
- Append Cost in query planners
- From: Nimesh Satam
- Re: Append Cost in query planners
- From: Heikki Linnakangas
- Re: Append Cost in query planners
- From: Heikki Linnakangas
- Re: Append Cost in query planners
- From: Nimesh Satam
- Re: Append Cost in query planners
- From: Heikki Linnakangas
- Re: Append Cost in query planners
- From: Nimesh Satam
- Append Cost in query planners
- Prev by Date: Re: partitioned table and ORDER BY indexed_field DESC LIMIT 1
- Next by Date: Re: Suggestions on an update query
- Previous by thread: Re: Append Cost in query planners
- Next by thread: Outer joins and Seq scans
- Indexes: