|
wantfly-pb,
Thanks for the pointer to Tom's Q&A. The words you quoted are about the resource usage of actual moving of data. That is, once you give the permission for row movement, moving the rows (as in case of alter table shrink space) will "consume processing resources...". My question is, Is leaving a table row movement enabled a bad idea? I think his answer at "March 10, 2009 - 2am" is what I need, "Any overhead? No, it is just permission to change a rowid if you do an operation that would cause a rowid to change - like...".
By the way, shrinking a table does not change the index to unusable as moving a table does. In fact, shrinking a table doesn't change the table's last_ddl_time either (but will change the index's), and doesn't invalidate the cursor using the table. It's a strange DDL in this respect.
Yong Huang |
|