db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1160) Document use of SPACE_TABLE to tell for tables and indexes: a) the number of pages allocated b) the number of empty pages
Date Thu, 03 Dec 2009 09:36:22 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785238#action_12785238
] 

Knut Anders Hatlen commented on DERBY-1160:
-------------------------------------------

I think it would be best not to have links to the javadoc because the URL may change and the
content is not stable (the URL points to the development sources which may not match the version
documented by the manual). It would be good, though, to capture the information from the javadoc
in the reference manual. As far as I can see, only the javadoc documents the columns in the
space table.

> Document use of SPACE_TABLE to tell for tables and indexes: a) the number of pages allocated
 b) the number of empty pages
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1160
>                 URL: https://issues.apache.org/jira/browse/DERBY-1160
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Stan Bradbury
>            Assignee: Bryan Pendleton
>         Attachments: cadminspace21579.html, docs.diff
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message