Re: Why does the query planner use two full indexes, when a dedicated partial index exists?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 19, 2012 at 3:49 PM, Richard Neill <rn214@xxxxxxxxxxxxxxxx> 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.ru@xxxxxxxxx


-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance


[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux