Re: Index Scans become Seq Scans after VACUUM ANALYSE

From: Justin Clift <justin(at)postgresql(dot)org>
To: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Lockhart <thomas(at)fourpalms(dot)org>, Jean-Paul ARGUDO <jean-paul(dot)argudo(at)idealx(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Index Scans become Seq Scans after VACUUM ANALYSE
Date: 2002-04-18 02:39:03
Message-ID: 3CBE31C7.1088B603@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-04-18 02:58:29 Re: SHOW ALL as a query result
Previous Message Thomas Lockhart 2002-04-18 02:38:09 Re: Index Scans become Seq Scans after VACUUM ANALYSE