From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: index-only scans |
Date: | 2011-08-12 20:06:37 |
Message-ID: | CA+TgmoZo0ZSFvDw1NSxYo+61rWVAV7JwgWS6A2TbJf3Nt9XkPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 12, 2011 at 4:03 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> On 11.08.2011 23:06, Robert Haas wrote:
>>
>> Comments, testing, review appreciated...
>
> I would've expected this to use an index-only scan:
>
> postgres=# CREATE TABLE foo AS SELECT generate_series(1,100000) AS id;
Ugh. I think there's something wrong with this test:
+ if (index->amcanreturn && !index->predOK && !index->indexprs)
I think that should probably say something like (ind->indpred == NIL
|| ind->predOK).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2011-08-12 20:11:05 | Re: Inserting heap tuples in bulk in COPY |
Previous Message | Robert Haas | 2011-08-12 20:03:56 | Re: VACUUM FULL versus system catalog cache invalidation |