Re: Index as hot block

From: hrishy <>
Date: Mon, 10 May 2010 14:54:24 +0000 (GMT)
Message-ID: <>


The application also uses selects with range predicates and that pretty much rules out a reverse key indexes.

The index block is hot because there are multiple sessions which perform a insert into this table.

  • On Mon, 10/5/10, <> wrote:

From: <> Subject: Re: Index as hot block
Date: Monday, 10 May, 2010, 13:36

Try a reverse key index.
Sent from my Verizon Wireless BlackBerry

From: hrishy <>
Date: Mon, 10 May 2010 11:08:52 +0000 (GMT) To: <>
Subject: Index as hot block


I have a partitioned table called mytable (a,b,c,d,e,f) partitioned by range on column a.

I need to enforce a unique constraint
currently the uniqueness is enforced by creating a locally partitioned index on myindx(c,b,a)
and this has become a hot block.

I was thinking of rebuilding that index and using myindx(a,b,c) can you guys let me know what your thoughts are ?


Received on Mon May 10 2010 - 09:54:24 CDT

Original text of this message