| From: | "Peterson, Bjorn" <Bjorn(dot)Peterson(at)pearson(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | enable_XXX options |
| Date: | 2005-04-01 16:04:08 |
| Message-ID: | 42E7C401A4CBCD49829BB53DDD538BA40211439B@chmpgexgmail3.ic.ncs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
I have a query in my application that takes an unreasonable amount of time
to complete (>4.5 hours execution time). After reviewing the EXPLAIN and
EXPLAIN ANALYZE output for that and similar queries, my colleagues and I
determined that turning off the enable_nestloop option might help - we
noticed dramatic speed improvements for that specific query after doing so
(<2 minutes execution time). I was warned not to mess with the enable_XXX
options in a production environment, but does anyone see any problem with
turning off the enable_nestloop option right before executing my query and
turning it back on afterwards?
Bjorn Peterson
Software Engineer
Pearson School Technologies
Bloomington, MN
(952) 681-3384
****************************************************************************
This email may contain confidential material.
If you were not an intended recipient,
Please notify the sender and delete all copies.
We may monitor email to and from our network.
****************************************************************************
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keith Worthington | 2005-04-01 16:20:25 | Triggers with FOR EACH STATEMENT |
| Previous Message | Mindaugas Riauba | 2005-04-01 14:54:44 | Tuning PostgreSQL |