| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | mlw <markw(at)mohawksoft(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index Scans become Seq Scans after VACUUM ANALYSE |
| Date: | 2002-04-18 15:43:11 |
| Message-ID: | 12544.1019144591@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
mlw <markw(at)mohawksoft(dot)com> writes:
> My one most important experience (I've had more than one) with this
> whole topic is DMN's music database, when PostgreSQL uses the index,
> the query executes in a fraction of a second. When
> "enable_seqscan=true" PostgreSQL refuses to use the index, and the
> query takes a about a minute. No matter how much I analyze, I have to
> disable sequential scan for the system to work correctly.
It would be useful to see "explain analyze" not just "explain" for these
cases. Also, what stats does pg_stats show for the variables used?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexandre Dulaunoy | 2002-04-18 15:47:15 | Re: new food for the contrib/ directory |
| Previous Message | Bruce Momjian | 2002-04-18 15:36:06 | Re: [SQL] A bug in gistPageAddItem()/gist_tuple_replacekey() |