On Mon, 03 Sep 2007 21:10:06 -0400
Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
> Shawn <postgres@xxxxxxxxxxxxxxx> writes:
> > You weren't kidding, that really made a difference. its .5 sec now
> > on the run. I think the vacuuming not running for a few weeks is
> > what got me. I caught an edit that had stopped the vacuuming
> > routine a while back. That must have been what caused the index
> > bloat.
>
> Hmm, but no vacuuming at all would have allowed the table itself to
> bloat too. Did you do a VACUUM FULL to recover after you noticed
> the size problem? The trouble with VACUUM FULL is it compresses the
> table but doesn't do a dang thing for indexes ...
>
> regards, tom lane
>
Thanks again to the list. I ran the reindex command that Tom suggested
and things seem to be holding. Even the vacuum command is running
faster. The whole script runs in about 10 seconds, far more acceptable.
Thanks Guys!
Shawn
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
