From: | Richard van den Berg <richard(dot)vandenberg(at)trust-factory(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-perform <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: When are index scans used over seq scans? |
Date: | 2005-04-22 09:04:17 |
Message-ID: | 4268BE11.6070200@trust-factory.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Tom Lane wrote:
> Are the tables in question particularly wide (many columns)?
Yes they are. They both have 20 columns. If I cut down the duration
table to just 1 column of timestamps, the planner uses the index.
Interesting, so I could store just the timestamps in another table (view
doesn't help) to speed up this query.
I am using the debian package. How can I tell if profiling is enabled?
Thanks a lot,
--
Richard van den Berg, CISSP
-------------------------------------------
Trust Factory B.V. | www.dna-portal.net
Bazarstraat 44a | www.trust-factory.com
2518AK The Hague | Phone: +31 70 3620684
The Netherlands | Fax : +31 70 3603009
-------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2005-04-22 09:47:31 | Re: Joel's Performance Issues WAS : Opteron vs Xeon |
Previous Message | David Roussel | 2005-04-22 08:44:05 | Re: Index bloat problem? |