Re: Equivalent praxis to CLUSTERED INDEX? - Mailing list pgsql-performance

From Jim C. Nasby
Subject Re: Equivalent praxis to CLUSTERED INDEX?
Date
Msg-id 20040831215013.GJ78395@decibel.org
Whole thread Raw
In response to Re: Equivalent praxis to CLUSTERED INDEX?  ("J. Andrew Rogers" <jrogers@neopolitan.com>)
List pgsql-performance
On Thu, Aug 26, 2004 at 12:04:48PM -0700, J. Andrew Rogers wrote:
> The major caveat to having tables of this type is that you can only have
> a primary key index.  No other indexes are possible because the "heap"
> constantly undergoes local reorganizations if you have a lot of write
> traffic, the same kind of reorganization you would normally expect in a
> BTree index.

This isn't true, at least in 9i. You can create whatever indexes you
want on an index-organized table. I believe that the index stores the PK
value instead of the ROWID.
--
Jim C. Nasby, Database Consultant               decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

pgsql-performance by date:

Previous
From: jelle
Date:
Subject: Re: Context Switching issue: Spinlock doesn't fix.
Next
From: Josh Berkus
Date:
Subject: Re: Context Switching issue: Spinlock doesn't fix.