Re: Unused Indexes
От | EDMUND DENGLER |
---|---|
Тема | Re: Unused Indexes |
Дата | |
Msg-id | 20030730135052.6B6D5D1C4CB@svr1.postgresql.org обсуждение исходный текст |
Ответ на | Unused Indexes (Tim McAuley <mcauleyt@tcd.ie>) |
Список | pgsql-general |
You need to convert the int's to bigints. select id where col1 = 1::bigint and col2 = 1::bigint Regards, Ed -----Original Message----- From: Tim McAuley <mcauleyt@tcd.ie> Date: Wed, 30 Jul 2003 13:46:46 To:pgsql-general@postgresql.org Subject: [GENERAL] Unused Indexes Hi, I have a table which I have populated with over 5000 entries. There is a combined index placed on two of the columns (both bigint). I am trying a simple select (i.e. select id where col1 = 1 and col2 = 1) covering these two columns and it keeps using a seq scan. Is this correct? I would have thought that with this number of entries that an index scan should be used. I am testing this using postgresql 7.3.3 on windows 2000 using cygwin. Doing "set enable_seqscan to off" does not change the results of the explain operation. I also tried setting a single index on just one of the columns and running an appropriate search; it still uses a seq scan. At what stage will the planner normally start using an index scan? Any hints appreciated. Tim ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
В списке pgsql-general по дате отправления: