Re: Index Scans become Seq Scans after VACUUM ANALYSE

Justin Clift <justin@postgresql.org>

From: Justin Clift <justin@postgresql.org>
To: Thomas Lockhart <lockhart@fourpalms.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Thomas Lockhart <thomas@fourpalms.org>, Jean-Paul ARGUDO <jean-paul.argudo@idealx.com>, pgsql-hackers@postgresql.org
Date: 2002-04-18T02:39:03Z
Lists: pgsql-hackers
Thomas Lockhart wrote:
> 
> ...
> > I'm of a belief that *eventually* we really can take enough of the
> > variables into consideration for planning the best query every time.  I
> > didn't say it was gunna be soon, nor easy though.
> 
> I agree. But I'd like to eliminate the optimizer variability which
> depends solely on the syntactical differences between traditional and
> "join syntax" inner join queries. If the reason for these differences
> are to allow explicit control over join order, let's get another
> mechanism for doing that.

Ok.  I see what you mean now.

That makes more sense.  :)

+ Justin


>                    - Thomas

-- 
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
   - Indira Gandhi