pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark R. Dingee <mark.dingee@cox.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re:
Date: Tue, 09 May 2006 19:51:46 -0400
Message-ID: <1147218706.6056.0.camel@elrond> (raw)
In-Reply-To: <17435.1147208476@sss.pgh.pa.us>
References: <15254425.1147204995912.JavaMail.root@eastrmwml05.mgt.cox.net>
	<17435.1147208476@sss.pgh.pa.us>

Tom,

Thanks for the advice.  I'll track it over the next couple weeks and see
what comes up.

Mark

On Tue, 2006-05-09 at 17:01 -0400, Tom Lane wrote:
> <mark.dingee@cox.net> writes:
> > I had an odd situation occur this morning with PGSQL 7.4 run on Red Hat Enterprise 4 (update 3) and could really use some wisdom.  
> 
> > ...  Single postmaster running.
> > ...  vacuum full is run every night as part of a cron job
> > ...  At start, data files consume about 28 GB
> > ...  This morning I dropped the database and reloaded from current backup
> > ... New instance consumes about 6 GB
> 
> > I can only assume that the database was not compacted, but I thought vacuum full performed that function along with tuple maintenance.  Can anyone expound on the problem and suggest a solution other than dropping and reloading the database?
> 
> The evidence is mostly gone now, but what I'd suggest is waiting a while
> to see if it bloats again, and if so finding out exactly *where* the
> bloat is.  Make some notes now about the sizes of your tables and
> indexes, and see what's getting larger.
> 
> My guess offhand is that the problem is index bloat.  VACUUM FULL not
> only doesn't help much with that, it tends to make it worse.  If the
> database size is supposed to be fairly stable, you'd probably be better
> off with a maintenance regime that doesn't use VACUUM FULL but just
> plain VACUUM.  Make sure your FSM settings are high enough.
> 
> 			regards, tom lane




view thread (3+ messages)

Message-ID: <1147218706.6056.0.camel@elrond>
Permalink:  ../1147218706.6056.0.camel@elrond/
Also on:    postgresql.org/message-id/1147218706.6056.0.camel@elrond

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: mark.dingee@cox.net, tgl@sss.pgh.pa.us
  Subject: Re: 
  In-Reply-To: <1147218706.6056.0.camel@elrond>
  References: <15254425.1147204995912.JavaMail.root@eastrmwml05.mgt.cox.net> <17435.1147208476@sss.pgh.pa.us> <1147218706.6056.0.camel@elrond>

* 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