Yes I ANALYZE the table, but no change for wastedispace. On Wed, Sep 21, 2011 at 1:06 PM, Guillaume Lelarge <guilla...@lelarge.info>wrote:
> On Wed, 2011-09-21 at 13:01 +0600, AI Rumman wrote: > > I am using Postgresql 9.0.1. > > > > Using the query http://wiki.postgresql.org/wiki/Show_database_bloat, I > got > > the following result for a table: > > > > -[ RECORD 1 ]----+----------------------------------------------- > > current_database | crm > > schemaname | public > > tablename | _attachments > > tbloat | 0.9 > > wastedbytes | 0 > > iname | attachments_description_type_attachmentsid_idx > > ibloat | 2.3 > > wastedibytes | 5439488 > > -[ RECORD 2 ]----+----------------------------------------------- > > current_database | crm > > schemaname | public > > tablename | _attachments > > tbloat | 0.9 > > wastedbytes | 0 > > iname | attachments_attachmentsid_idx > > ibloat | 0.2 > > wastedibytes | 0 > > -[ RECORD 3 ]----+----------------------------------------------- > > current_database | crm > > schemaname | public > > tablename | _attachments > > tbloat | 0.9 > > wastedbytes | 0 > > iname | _attachments_pkey > > ibloat | 0.2 > > wastedibytes | 0 > > > > I REINDEXED both the indexes and table, but I did not find any change in > > wastedspace or wastedispace. > > Could you please tell me why? > > REINDEX only rebuilds indexes. And you'll obviously have a bit of "lost > space" because of the FILLFACTOR value (90% on indexes IIRC). > > > -- > Guillaume > http://blog.guillaume.lelarge.info > http://www.dalibo.com > >
