You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <de...@db.apache.org> on 2006/03/29 00:50:20 UTC
[jira] Commented: (DERBY-1160) Need a documented way to tell for
tables and indexes: a) the number of pages allocated b) the number of
empty pages
[ http://issues.apache.org/jira/browse/DERBY-1160?page=comments#action_12372157 ]
Bryan Pendleton commented on DERBY-1160:
----------------------------------------
Once such a technique is made available, here would be a good place in the documentation to describe it:
http://db.apache.org/derby/docs/10.1/adminguide/cadminspace21579.html
> Need a documented way to tell for tables and indexes: a) the number of pages allocated b) the number of empty pages
> --------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1160
> URL: http://issues.apache.org/jira/browse/DERBY-1160
> Project: Derby
> Type: Improvement
> Reporter: Stan Bradbury
>
> Very active systems would benefit from a documented way to determine how many empty pages are allocated to an index or table in order to determine whether a COMPRESS_TABLE is worth running.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira