pg_atributes index space question

Lists: pgsql-general
From: Joe Maldonado <jmaldonado(at)webehosting(dot)biz>
To: pgsql-general(at)postgresql(dot)org
Subject: pg_atributes index space question
Date: 2005-03-18 13:35:22
Message-ID: 423AD91A.1020202@webehosting.biz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general

Hello,

After a VACUUM FULL I saw that pg_attribute tables indexes haven't
been deleted as reported by a subsequent vacuum analyze. But the pages
corresponding to just the table has been deleted to 196 pages from
about 181557 pages. Are all system tables affected by this ? How can
we reclaim this space without shutting down postmaster ? Is this fixed
in any new release ?

db=# select relpages, reltuples from pg_catalog.pg_class where
relname = 'pg_attribute';
relpages | reltuples
----------+-----------
196 | 9965
(1 row)

db=# vacuum verbose analyze pg_catalog.pg_attribute;
INFO: vacuuming "pg_catalog.pg_attribute"
INFO: index "pg_attribute_relid_attnam_index" now contains 9965 row
versions in 181557 pages
DETAIL: 1518 index row versions were removed.
181263 index pages have been deleted, 20000 are currently reusable.

thanks


From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Maldonado <jmaldonado(at)webehosting(dot)biz>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_atributes index space question
Date: 2005-03-18 15:29:29
Message-ID: 6779.1111159769@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general

Joe Maldonado <jmaldonado(at)webehosting(dot)biz> writes:
> db=# vacuum verbose analyze pg_catalog.pg_attribute;
> INFO: vacuuming "pg_catalog.pg_attribute"
> INFO: index "pg_attribute_relid_attnam_index" now contains 9965 row
> versions in 181557 pages

REINDEX is probably the only realistic way to fix that. It shouldn't
take very long, fortunately, so the exclusive lock shouldn't be an
enormous problem.

regards, tom lane