Yes, Index can help a lot. But actually there has been five indices. The table takes 1.4G space while the indices take 2.3G. The select sentence is still slow. :( On Tue, Mar 25, 2008 at 11:50 AM, Chris <dmagick@xxxxxxxxx> wrote: > Shelley wrote: > > Hi all, > > > > I made a post a week ago to ask for the idea of the fastest way to get > > table records. > > Fyi, > > > http://phparch.cn/index.php/mysql/35-MySQL-programming/126-fastest-way-to-get-total-records-from-a-table > > > > > > Look at the time even a 'count(1)' took. > > Then you can imagine how much time sql such as "select a,b from > > table_name where c='d'" will take. > > > > I have a lot of tables like that. So my questions is: > > What's your practice to optimize tables like that? > > I pretty much follow what I've said in this article: > > http://www.designmagick.com/article/16/PostgreSQL/How-to-index-a-database > > -- > Postgresql & php tutorials > http://www.designmagick.com/ > -- Regards, Shelley
