Re: Index Scans become Seq Scans after VACUUM ANALYSE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Loftis <mloftis(at)wgops(dot)com>
Cc: Louis-David Mitterrand <vindex(at)apartia(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Index Scans become Seq Scans after VACUUM ANALYSE
Date: 2002-04-17 03:52:53
Message-ID: 3171.1019015573@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Loftis <mloftis(at)wgops(dot)com> writes:
> Reading all of this discussion lately about how the planner seems to
> prefer seqscan's in alot of places where indexes would be better starts
> making me wonder if some of the assumptions or cals made to figure costs
> are wrong...

Could well be. The sources are open, feel free to take a look ...
src/backend/optimizer/path/costsize.c is the epicenter ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-04-17 03:58:09 Re: Index Scans become Seq Scans after VACUUM ANALYSE
Previous Message Rod Taylor 2002-04-17 02:29:10 Re: [BUGS] Foreign Key woes -- 7.2 and ~7.3