Re: select/delete on IOT becomes slower as more rows get deleted

From: 조동욱 <ukja.dion@xxxxxxxxx>
To: nigel.cl.thomas@xxxxxxxxxxxxxx
Date: Thu, 5 Feb 2009 11:16:28 +0900

Yes, I think that Richard gave OP the exact explanation.

As more keys are deleted from IOT(index), the select statement would read
more blocks to retrieve first key.



================================
Dion Cho - Oracle Performance Storyteller

http://dioncho.wordpress.com (english)
http://ukja.tistory.com (korean)
================================

References:
- Re: select/delete on IOT becomes slower as more rows get deleted
  - From: Ian Cary
- Re: select/delete on IOT becomes slower as more rows get deleted
  - From: Andrew Kerber
- Re: select/delete on IOT becomes slower as more rows get deleted
  - From: Nigel Thomas

Other related posts:

» select/delete on IOT becomes slower as more rows get deleted- Martin Berger
» Re: select/delete on IOT becomes slower as more rows get deleted- Ian Cary
» Re: select/delete on IOT becomes slower as more rows get deleted- Andrew Kerber
» Re: select/delete on IOT becomes slower as more rows get deleted- Nigel Thomas
» Re: select/delete on IOT becomes slower as more rows get deleted - 조동욱