Re: Why does the query planner use two full indexes, when a dedicated partial index exists?
| От | Sergey Konoplev |
|---|---|
| Тема | Re: Why does the query planner use two full indexes, when a dedicated partial index exists? |
| Дата | |
| Msg-id | CAL_0b1s6_YZDdzt3NizwC8X+dYA37T-4aZOTzw3KJ3-iXuSjjw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Why does the query planner use two full indexes, when a dedicated partial index exists? (Richard Neill <rn214@richardneill.org>) |
| Ответы |
Re: Why does the query planner use two full indexes, when
a dedicated partial index exists?
|
| Список | pgsql-performance |
Hi, On Wed, Dec 19, 2012 at 1:13 PM, Richard Neill <rn214@richardneill.org> wrote: > Index Scan using tbl_tracker_performance_1_idx on tbl_tracker > (cost=0.00..5440.83 rows=1 width=174) (actual time=0.052..0.052 rows=0 > loops=1) > Index Cond: (parcel_id_code = 53030) It looks like your index is bloated. Have you had a lot of updates/deletes on rows with exit_state is null? Try to reindex tbl_tracker_performance_1_idx. To reindex it without locks create a new index with temporary name concurrently, delete the old one and rename the new one using the old name. -- Sergey Konoplev Database and Software Architect http://www.linkedin.com/in/grayhemp Phones: USA +1 415 867 9984 Russia, Moscow +7 901 903 0499 Russia, Krasnodar +7 988 888 1979 Skype: gray-hemp Jabber: gray.ru@gmail.com
В списке pgsql-performance по дате отправления: