Re: Planner chooses multi-column index in 9.2 when maybe it should not - Mailing list pgsql-general

From Tom Lane
Subject Re: Planner chooses multi-column index in 9.2 when maybe it should not
Date
Msg-id 13660.1349913045@sss.pgh.pa.us
Whole thread Raw
In response to Re: Planner chooses multi-column index in 9.2 when maybe it should not  (Greg Sabino Mullane <greg@endpoint.com>)
List pgsql-general
Greg Sabino Mullane <greg@endpoint.com> 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


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Index only scan
Next
From: Ondrej Ivanič
Date:
Subject: Re: moving from MySQL to pgsql