Re: myschema - extent size looks very large
From: Gary Quiring <garyq@emcosales.com>
>
>Newbie alert!! I ran myschema -d <db> -a and found the extent sizes to
>look very large. I also used 'extentreport' from Matthew Devlin and the
>report for this table looks like this:
It doesn't matter if you have too few extents and they're big. Too many
extents is a problem.
>-----------------------------------------------------------------------------
> First Next Total Used Num Num
>Table Extent Extent Size Kb Extents Rows
>-----------------------------------------------------------------------------
>inv_shp_l 16 8192 223008 217874 155 563222
>
>Thanks
>Gary Quiring
>
>
>Output from myschema:
>REVOKE ALL ON "informix".quot_l FROM public;>CREATE TABLE "informix".inv_shp_l (
> inv_shp_l_id SERIAL(-2147110047) {Curr: 1} NOT NULL,
><snip>
> item_w_m_id INTEGER
>) IN data2dbs EXTENT SIZE 217874 NEXT SIZE 16 LOCK MODE ROW;
>
>{
> Current first extend (16) too small!
> Actual pages used by table has been used.
> Tablespace header reports -
> Total: pgsused=108937, pgsdata=93871.
> Please review extent sizing and adjust to allow for growth.
>}
>
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com