Re: The need for clustered indexes to boost TPC-V performance
Robert Klemme <shortcutter@googlemail.com>
From: Robert Klemme <shortcutter@googlemail.com>
To: Reza Taheri <rtaheri@vmware.com>
Cc: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>, "Andy Bond (abond@redhat.com)" <abond@redhat.com>, Greg Kopczynski <gregwk@vmware.com>, Jignesh Shah <jshah@vmware.com>
Date: 2012-07-05T12:30:23Z
Lists: pgsql-performance, pgsql-general
On Wed, Jul 4, 2012 at 1:13 AM, Reza Taheri <rtaheri@vmware.com> wrote: > Checking online, the subject of clustered indexes for PostgreSQL comes up > often. PGSQL does have a concept called “clustered table”, which means a > table has been organized in the order of an index. This would help with > sequential accesses to a table, but has nothing to do with this problem. > PGSQL folks sometimes refer to what we want as “integrated index”. I do understand this correctly that we are speaking about the concept which is known under the term "index organized table" (IOT) in Oracle land, correct? http://docs.oracle.com/cd/E11882_01/server.112/e25789/indexiot.htm#CBBJEBIH Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/
Commits
-
Support index-only scans using the visibility map to avoid heap fetches.
- a2822fb9337a 9.2.0 cited