| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
|---|---|
| To: | Richard Neill <rn214(at)richardneill(dot)org> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Why does the query planner use two full indexes, when a dedicated partial index exists? |
| Date: | 2012-12-20 00:08:58 |
| Message-ID: | CAL_0b1t5_h-VUE+sL2cfd1E78xYOq9T7P3n31iZhLT3vEa=mOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Dec 19, 2012 at 3:49 PM, Richard Neill <rn214(at)richardneill(dot)org> wrote:
> * The reindex solution doesn't work. I just tried it, and the query planner
> is still using the wrong indexes.
Can you show the explain analyze with tbl_tracker_performance_1_idx
straight after reindex (eg. before it has been bloated again)?
> * If the tbl_tracker_performance_1_idx had indeed become bloated, wouldn't
> that have meant that when the query planner was forced to use it (by
> deleting the alternative indexes), it would have been slow?
It is hard to say. There might be a bloating threshold after with it
will be slow. Also it depends on the index column values.
--
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(dot)ru(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Neill | 2012-12-20 00:22:49 | Re: Why does the query planner use two full indexes, when a dedicated partial index exists? |
| Previous Message | Richard Neill | 2012-12-19 23:49:34 | Re: Why does the query planner use two full indexes, when a dedicated partial index exists? |