Re: Index Scans become Seq Scans after VACUUM ANALYSE

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Justin Clift <justin(at)postgresql(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:38:09
Message-ID: 3CBE3191.99192319@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

...
> 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.

- Thomas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Clift 2002-04-18 02:39:03 Re: Index Scans become Seq Scans after VACUUM ANALYSE
Previous Message Justin Clift 2002-04-18 02:30:54 Re: Index Scans become Seq Scans after VACUUM ANALYSE