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 30DE7EFF8E for ; Thu, 5 Jun 2003 16:39:36 +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 29897-07 for ; Thu, 5 Jun 2003 16:39:34 +0000 (GMT) Received: from mail.libertyrms.com (unknown [209.167.124.227]) by svr1.postgresql.org (Postfix) with ESMTP id 53F9AEFF8D for ; Thu, 5 Jun 2003 16:39:34 +0000 (GMT) Received: from [10.1.2.130] (helo=dba2) by mail.libertyrms.com with esmtp (Exim 3.22 #3 (Debian)) id 19Nxm3-0000O1-00 for ; Thu, 05 Jun 2003 12:39:35 -0400 Received: by dba2 (Postfix, from userid 1019) id 3F0BED763; Thu, 5 Jun 2003 12:39:34 -0400 (EDT) Date: Thu, 5 Jun 2003 12:39:34 -0400 From: Andrew Sullivan To: pgsql-performance Subject: Re: Enabling and disabling run time configuration parameters. Message-ID: <20030605163934.GE4178@libertyrms.info> Mail-Followup-To: Andrew Sullivan , pgsql-performance References: <3EDF633A.8000502@netscape.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EDF633A.8000502@netscape.net> User-Agent: Mutt/1.5.4i X-Archive-Number: 200306/20 X-Sequence-Number: 2104 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 M2P 2A8 +1 416 646 3304 x110