All right ... after reading up on the documentation for vacuum, I
understand why that's necessary. I've run vacuum analyze on all the
tables, now. Here are the more realistic results from explain:
NOTICE: QUERY PLAN:
Sort (cost=62.46..62.46 rows=14 width=64)
-> Nested Loop (cost=0.00..62.19 rows=14 width=64)
-> Index Scan using pk_tblsidedruglink on tblsidedruglink
(cost=0.00..33.82 rows=14 width=28)
-> Index Scan using pk_tblmedcond on tblmedcond
(cost=0.00..2.01 rows=1 width=36)
The query runs lightning fast now ... THANK YOU!!! :)
-Brice
Stephan Szabo wrote:
>
> After you load the data, you need to run vacuum analzye. That'll
> get statistics on the current data in the table. Of course, I'm
> not sure that'll help in this case.
>
> On Thu, 8 Feb 2001, Brice Ruth wrote:
>
> > Stephan,
> >
> > Here is what EXPLAIN shows:
> >
> > NOTICE: QUERY PLAN:
> >
> > Sort (cost=0.02..0.02 rows=1 width=64)
> > -> Nested Loop (cost=0.00..0.01 rows=1 width=64)
> > -> Seq Scan on tblmedcond (cost=0.00..0.00 rows=1 width=36)
> > -> Seq Scan on tblsidedruglink (cost=0.00..0.00 rows=1 width=28)
> >
> > As for vacuum analyze - prior to running into these problems, I deleted
> > all data from the database (using delete from <tblname>) and then ran
> > vacuumdb -a, after which I loaded the data into the tables using 'copy
> > ... from' - there have been no updates to the database since then -
> > merely selects.
--
Brice Ruth
WebProjkt, Inc.
VP, Director of Internet Technology
http://www.webprojkt.com/
