Received: from jupiter.hub.org (jupiter.hub.org [64.49.215.5]) by postgresql.org (Postfix) with ESMTP id EF9C34760A3 for ; Fri, 22 Mar 2002 09:43:01 -0500 (EST) Received: (from news@localhost) by jupiter.hub.org (8.11.6/8.11.6) id g2MEeko76187 for pgsql-general@postgresql.org; Fri, 22 Mar 2002 08:40:46 -0600 (CST) (envelope-from news) From: "Pirtea Calin" X-Newsgroups: comp.databases.postgresql.general, comp.databases.postgresql.questions Subject: Re: Yet another indexing issue. Date: Fri, 22 Mar 2002 16:37:31 +0200 Organization: Hub.Org Networking Services (http://www.hub.org) Lines: 25 Message-ID: References: <20020319155803.G37657-100000@megazone23.bigpanda.com> Reply-To: "Pirtea Calin" Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Complaints-To: news@hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 To: pgsql-general@postgresql.org X-Archive-Number: 200203/1128 X-Sequence-Number: 22491 > > Where would one find set enable_seqscan=off; in the docs? > > To be honest I'm not sure where it's mentioned. It's a big tool that > lets you make some gross changes to the optimizer's planning (sets the > cost of sequence scan very very high). > I found this in Admin.pdf 3.4.1. Planner and Optimizer Tuning page 37/38 ENABLE_SEQSCAN (boolean) Enables or disables the query planner's use of sequential scan plan types. It's not possible to suppress sequential scans entirely, but turning this variable off discourages the planner from using one if there is any other method available. The default is on. This is mostly useful to debug the query planner. -- Best regards, Aplication Developer Pirtea Calin Iancu S.C. SoftScape S.R.L. pcalin@rdsor.ro