Re: The need for clustered indexes to boost TPC-V performance
Reza Taheri <rtaheri@vmware.com>
From: Reza Taheri <rtaheri@vmware.com>
To: Robert Klemme <shortcutter@googlemail.com>
Cc: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Date: 2012-07-05T19:13:09Z
Lists: pgsql-performance, pgsql-general
Hi Robert, Yes, the same concept. Oracle's IOT feature is used often with TPC benchmarks. Thanks, Reza > -----Original Message----- > From: Robert Klemme [mailto:shortcutter@googlemail.com] > Sent: Thursday, July 05, 2012 5:30 AM > To: Reza Taheri > Cc: pgsql-performance@postgresql.org; Andy Bond (abond@redhat.com); > Greg Kopczynski; Jignesh Shah > Subject: Re: [PERFORM] The need for clustered indexes to boost TPC-V > performance > > 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#CBB > JEBIH > > 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