Re: BUG #8447: With table inheritance, indexes seems to be ignored when looking over indexed fields in base table

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: "stormbyte(at)gmail(dot)com" <stormbyte(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #8447: With table inheritance, indexes seems to be ignored when looking over indexed fields in base table
Date: 2013-09-12 15:19:46
Message-ID: 1378999186.30712.YahooMailNeo@web162902.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"stormbyte(at)gmail(dot)com" <stormbyte(at)gmail(dot)com> wrote:

> [ Seq Scan is used on empty relation, rather than Index Scan ]

> This is not the expected result.  [ ... ] it is still using
> sequential scan rather than what would be expected: Index Scan

This is not a bug.

If statistics indicate that all rows can be accessed with one page
access (to the heap) why should it use an index?

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message pulsack.heike 2013-09-12 15:21:47 BUG #8449: ODBC Failure with Access 10
Previous Message laszlo.rozsahegyi 2013-09-12 14:41:01 BUG #8448: looping through query results exits at 10th step under some conditions