Re: index skipped in favor of seq scan.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ryan(dot)a(dot)roemmich(at)mail(dot)sprint(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: index skipped in favor of seq scan.
Date: 2001-07-10 21:33:59
Message-ID: 10756.994800839@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

ryan(dot)a(dot)roemmich(at)mail(dot)sprint(dot)com writes:
> Does the planner make the choice based on a percentage?

Essentially (actually, it's a nonlinear cost model, so "percentage" is
too simplistic).

It sounds like the only solution available to you until 7.2 comes out
is to use a sledgehammer:

set enable_seqscan to off;

See the documentation.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2001-07-10 22:03:34 Re: Re: Too much data received?
Previous Message Mihai Gheorghiu 2001-07-10 21:30:36 Re: Interfacing with MSAccess