Re: Yet another indexing issue.

From: "Pirtea Calin" <pcalin(at)rdsor(dot)ro>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Yet another indexing issue.
Date: 2002-03-22 14:37:31
Message-ID: a7ffpa$29sh$1@jupiter.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-sql

> > 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(at)rdsor(dot)ro

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-03-22 15:21:04 Re: Huge Performance Difference on Similar Query in Pg7.2
Previous Message Maarten.Boekhold 2002-03-22 14:34:41 Have you seen these hackers: Uncle George

Browse pgsql-sql by date

  From Date Subject
Next Message Richard Huxton 2002-03-22 16:15:06 Re: How to return more than one variable from PgPlSQL procedure?
Previous Message Ivan Babikov 2002-03-22 12:34:05 How to return more than one variable from PgPlSQL procedure?