| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Visibility map thoughts |
| Date: | 2007-11-08 09:21:50 |
| Message-ID: | 4732D52E.6010602@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kevin Grittner wrote:
> I know this issue on this thread has come up at least one or two
> other times lately:
>
> http://archives.postgresql.org/pgsql-performance/2007-08/msg00113.php
>
> I know it's a largely independent issue, but your comment about the
> API not giving access to the index tuples echoed comments regarding
> what it would take to allow optimizations in this area.
If we do separate the index scan and heap fetch to two executor nodes,
it would handle that case as well, I think. It's not directly related to
index-only scans, but returning data from an index is required for that
as well.
It wouldn't be a bitmap index scan anymore, BTW.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Smet | 2007-11-08 10:08:33 | Re: Estimation problem with a LIKE clause containing a / |
| Previous Message | Brendan Jurd | 2007-11-08 08:36:40 | Re: A small rant about coding style for backend functions |