X-Original-To: pgsql-performance@postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by developer.postgresql.org (Postfix) with ESMTP id 29CAF925DC2 for ; Fri, 30 May 2003 16:33:14 -0400 (EDT) Received: from developer.postgresql.org ([64.117.224.193]) by localhost (developer.postgresql.org [64.117.224.193:10024]) (amavisd-new) with ESMTP id 05541-05 for ; Fri, 30 May 2003 16:33:13 -0400 (EDT) Received: from imo-d01.mx.aol.com (imo-d01.mx.aol.com [205.188.157.33]) by developer.postgresql.org (Postfix) with ESMTP id BC8EA925DB9 for ; Fri, 30 May 2003 16:33:12 -0400 (EDT) Received: from yusuf0478@netscape.net by imo-d01.mx.aol.com (mail_out_v36.3.) id k.7.8cea604 (22681) for ; Fri, 30 May 2003 16:33:07 -0400 (EDT) Received: from netscape.net (66-163-11-108.ip.tor.radiant.net [66.163.11.108]) by air-in04.mx.aol.com (v93.12) with ESMTP id MAILININ42-58993ed7c003366; Fri, 30 May 2003 16:33:07 -0400 Message-ID: <3ED7C003.1090303@netscape.net> Date: Fri, 30 May 2003 16:33:07 -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 Sequencial Scan Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Mailer: Unknown (No Version) X-Virus-Scanned: by amavisd-new X-Archive-Number: 200305/292 X-Sequence-Number: 2071 In the application, that I'm working on, I have a query that'll be a lot 60% faster if I disable sequential scan forcing it to you my index. Is it bad practice to disable sequential scan ( set enable_seqscan=false), run my query then enable sequential scan, whenever I'm running this query? Why? Thanks in advance - David Wendy