From: Yusuf <yusuf0478@netscape.net>
To: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Enabling and disabling run time configuration parameters.
Date: Thu, 05 Jun 2003 11:35:22 -0400
Message-ID: <3EDF633A.8000502@netscape.net> (raw)
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.
I need to speed up an enterprise application that I'm working on, and I
wouldn't want to screw things up.
My plan is for every query that could be optimized by adjusting
parameters: I'll enable parameters that'll speed it up, run the query,
then set the parameters back to their default values.
Thanks in advance.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: yusuf0478@netscape.net
Subject: Re: Enabling and disabling run time configuration parameters.
In-Reply-To: <3EDF633A.8000502@netscape.net>
References: <3EDF633A.8000502@netscape.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox