From: | dx k9 <bitsandbytes88(at)hotmail(dot)com> |
---|---|
To: | posgres support <pgsql-admin(at)postgresql(dot)org> |
Subject: | check_postgres_bloat |
Date: | 2010-06-11 14:50:20 |
Message-ID: | SNT123-W2DB788D752D60727FF1D8D1D90@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
I'm running a the check_postgres.pl --action=bloat on a database and finding that there is wasted space.
I'm using 95% for the crtical %. If I use 110% I get the same things, but 115% shows everything is OK.
check_postgres_bloat -H host -p port -db thing -t thing1 -c 95%
check_postgres.pl version 2.14.3
postgres version 8.3.9
POSTGRES_BLOAT CRITICAL: service=thing1 (db thing) table public.thing1 rows:25537152 pages:212311 shouldbe:187545 (1.1X) wasted size:202883072 (193 MB) * (db thing) table public.thing2 rows:10109173 pages:101832 shouldbe:94016 (1.1X) wasted size:64028672 (61 MB) * (db thing) table thing3 rows:1184946 pages:28701 shouldbe:21434 (1.3X) wasted size:59531264 (56 MB) *
I have run a reindexdb on the table, full vacuum (fze), still I can't get the wasted size to go down on these, so I continue to get critical alerts that my tables are bloated.
check_postgres checks for both index and table bloat. It looks like my indexes are ok, this is just picking up on table bloat. I'm not sure what I can do to reclaim the wasted space other than vacuum full & analyze. Maybe a pgdump will do it.
Thanks for any insight,
~DjK
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2
From | Date | Subject | |
---|---|---|---|
Next Message | Kenneth Marshall | 2010-06-11 14:54:26 | Re: check_postgres_bloat |
Previous Message | Tom Lane | 2010-06-11 14:21:28 | Re: Server crash when using dblink_build_sql_* after alter table |