db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Updated: (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 04:24:20 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bryan Pendleton updated DERBY-1160:
-----------------------------------

    Attachment: cadminspace21579.html
                docs.diff

I'm uncertain about whether the pages in the doc set should contain direct references to the
internal javadoc, so for now I simply added some text to the admin guide page showing how
to use SPACE_TABLE to estimate the space
that could be reclaimed.

Is it reasonable for the doc pages to contain a direct XREF to
http://db.apache.org/derby/javadoc/engine/org/apache/derby/diag/SpaceTable.html ?


> 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