From: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
---|---|
To: | akp geek <akpgeek(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Table Bloat still there after the Vacuum |
Date: | 2010-04-26 15:38:42 |
Message-ID: | r2je94e14cd1004260838l789ec144oaa49b3ebe490e8a5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2010/4/26 Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>:
> 2010/4/26 akp geek <akpgeek(at)gmail(dot)com>:
>> Hi All -
>> I have a table bloated with following details
>> rows:29431 pages:516039 shouldbe:534 (966.4X) wasted size:4223016960 (3 GB)
>> *
>
> I think this info come from check_postgres nagios script.
> As said in the doc, this info is not 100% sure : it depend on the last
> analyze *and* the type the columns *and* the distribution of data in
> those columns.
> I suggest you to check the pg_stats.avg_width relative to this table.
>
> And, vacuum verbose information is good for diagnostics...
and the verbose said there is actually a problem :-)
check long running transaction, idle in connection, ... they prevent
the vacuum things
>
>> I did a vacuum on the database and also I did vacuumdb
>> full on the table. Still there is no change. Can you please suggest if there
>> is any other operation that can be done to take care of the issue
>> Thanks for the help
>>
>> Regards
>
>
>
> --
> Cédric Villemain
>
--
Cédric Villemain
From | Date | Subject | |
---|---|---|---|
Next Message | Vincenzo Romano | 2010-04-26 15:41:20 | Re: Inheritance efficiency |
Previous Message | akp geek | 2010-04-26 15:27:10 | Re: Table Bloat still there after the Vacuum |