| From: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
|---|---|
| To: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Enabling and disabling run time configuration parameters. |
| Date: | 2003-06-05 16:39:34 |
| Message-ID: | 20030605163934.GE4178@libertyrms.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Jun 05, 2003 at 11:35:22AM -0400, Yusuf wrote:
> I have discovered that I could optimize queries by adjusting the
> following parameters such as enable_seqscan, enable_hashjoin,
> enable_mergejoin and enable_nestloop.
>
> Is it a good idea, to temporarily adjust those values before running a
> query to spend up the execution time? I've searched online and wasn't
> able to find articles about it.
It sounds like you need more general tuning. If the planner is
making mistakes, it'd be nice to know about it. Could you post some
details?
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-06-05 16:42:01 | Re: Enabling and disabling run time configuration parameters. |
| Previous Message | Josh Berkus | 2003-06-05 16:19:10 | Re: Enabling and disabling run time configuration parameters. |