From: | Lutischán Ferenc <lutischanf(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Improve Seq scan performance |
Date: | 2008-11-10 06:50:43 |
Message-ID: | 4917D9C3.9060001@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Dear List,
I would like to improve seq scan performance. :-)
I have many cols in a table. I use only 1 col for search on it. It is
indexed with btree with text_pattern_ops. The search method is: r like
'%aaa%'
When I make another table with only this col values, the search time is
better when the data is cached. But wronger when the data isn't in cache.
I think the following:
- When there is a big table with many cols, the seq search is read all
cols not only searched.
- If we use an index with full values of a col, it is possible to seq
scan over the index is make better performance (lower io with smaller data).
It is possible to make an index on the table, and make a seq index scan
on this values?
Thanks for helping.
Best Regards,
Ferenc
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2008-11-10 06:55:55 | Re: Improve Seq scan performance |
Previous Message | Richard Huxton | 2008-11-07 10:45:50 | Re: PostgreSQL OR performance |