X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 72B36EFFFB for ; Thu, 5 Jun 2003 15:35:33 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 17511-03 for ; Thu, 5 Jun 2003 15:35:32 +0000 (GMT) Received: from imo-r01.mx.aol.com (imo-r01.mx.aol.com [152.163.225.97]) by svr1.postgresql.org (Postfix) with ESMTP id 99BB6EFFBA for ; Thu, 5 Jun 2003 15:35:31 +0000 (GMT) Received: from yusuf0478@netscape.net by imo-r01.mx.aol.com (mail_out_v36.3.) id k.c7.7dbf16e (16237) for ; Thu, 5 Jun 2003 11:35:23 -0400 (EDT) Received: from netscape.net (66-163-11-108.ip.tor.radiant.net [66.163.11.108]) by air-in03.mx.aol.com (v93.12) with ESMTP id MAILININ31-3f6d3edf633a17b; Thu, 05 Jun 2003 11:35:22 2000 Message-ID: <3EDF633A.8000502@netscape.net> Date: Thu, 05 Jun 2003 11:35:22 -0400 From: Yusuf User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-performance Subject: Enabling and disabling run time configuration parameters. Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Mailer: Unknown (No Version) X-Spam-Status: No, hits=0.6 tagged_above=0.0 required=5.0 tests=FROM_ENDS_IN_NUMS, USER_AGENT_MOZILLA_UA, X_ACCEPT_LANG X-Spam-Level: * X-Archive-Number: 200306/18 X-Sequence-Number: 2102 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.