pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: dx k9 <bitsandbytes88@hotmail.com>
To: posgres support <pgsql-admin@postgresql.org>
Subject: check_postgres_bloat
Date: Fri, 11 Jun 2010 10:50:20 -0400
Message-ID: <SNT123-W2DB788D752D60727FF1D8D1D90@phx.gbl> (raw)


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=

view thread (4+ messages)  latest in thread

Message-ID: <SNT123-W2DB788D752D60727FF1D8D1D90@phx.gbl>
Permalink:  ../SNT123-W2DB788D752D60727FF1D8D1D90@phx.gbl/
Also on:    postgresql.org/message-id/SNT123-W2DB788D752D60727FF1D8D1D90@phx.gbl

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: bitsandbytes88@hotmail.com
  Subject: Re: check_postgres_bloat
  In-Reply-To: <SNT123-W2DB788D752D60727FF1D8D1D90@phx.gbl>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox