Search Postgresql Archives

Re: Planner chooses multi-column index in 9.2 when maybe it should not

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

 



Greg Sabino Mullane <greg@xxxxxxxxxxxx> writes:
> Found a good demonstration of the problem. Here's explain analyze of a 
> query on 9.2 with enable_indexonlyscan = off; This produces the exact same 
> plan as 8.3. The tables in question have been analyzed. Changing 
> random_page_cost has no effect. The main foobar table has 17M rows. 

Can you provide a self-contained test case for this (ie, sample data)?

			regards, tom lane


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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux