Re: REINDEX not working for wastedspace
От | Venkat Balaji |
---|---|
Тема | Re: REINDEX not working for wastedspace |
Дата | |
Msg-id | CAFrxt0ixpDtSERgYyWN08zJws5K=boE0s0L9sCvtGfCiw8hOtQ@mail.gmail.com обсуждение исходный текст |
Ответ на | REINDEX not working for wastedspace (AI Rumman <rummandba@gmail.com>) |
Список | pgsql-performance |
Could you please let us know if you have analyzed after the re-indexing is done ?
This must show differences for only Indexes not the Tables.
For Tables, you need to do VACUUM FULL to show the difference.
Thanks
Venkat
On Wed, Sep 21, 2011 at 12:31 PM, AI Rumman <rummandba@gmail.com> 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?
В списке pgsql-performance по дате отправления: