Re: SourceForge & Postgres

one thing I've found to get around this is for any query that doesn't
appear to use the index properly, just do:

SET ENABLE_SEQSCAN=OFF;
<query>
SET ENABLE_SEQSCAN=ON;

that way for those queries that do work right, ou haven't forced it a
different route ..

On Mon, 11 Dec 2000, mlw wrote:

> Bruce Momjian wrote:
> > This is great news.  As far as the optimizer, any chance of testing 7.1
> > to see if it is improved.  I believe it has been over 7.0.3.
> 
> I just did a test of my database that exhibits this behavior, using 7.1
> from CVS.
> 
> When postmaster is started with "-o -fs" I get this:
> 
> cdinfo=# explain select * from ztitles where artistid = 0 ;
> NOTICE:  QUERY PLAN:
> 
> Index Scan using ztitles_artistid_ndx on ztitles  (cost=0.00..5915.01
> rows=3163 width=296)
> 
> EXPLAIN
> 
> When postmaster is started without "-o -fs" I get this:
> 
> cdinfo=# explain select * from ztitles where artistid = 0 ;
> NOTICE:  QUERY PLAN:
>  
> Seq Scan on ztitles  (cost=0.00..4740.75 rows=3163 width=296)
>  
> EXPLAIN 
> 
> -- 
> http://www.mohawksoft.com
> 

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org