pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: Christopher Browne <cbbrowne@ca.afilias.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: is pg_autovacuum so effective ?
Date: Wed, 23 Feb 2005 14:18:08 -0500
Message-ID: <421CD6F0.8010406@zeut.net> (raw)
In-Reply-To: <60psyr265t.fsf@dba2.int.libertyrms.com>
References: <cvg29i$2l69$1@news.hub.org>
	<12400.1109107683@sss.pgh.pa.us>
	<421BD64E.30803@bigfoot.com>
	<60psyr265t.fsf@dba2.int.libertyrms.com>

Christopher Browne wrote:

>Gaetano Mendola <mendola@bigfoot.com> writes:
>  
>
>>I do a graph about my disk usage and it's a ramp since one week,
>>I'll continue to wait in order to see if it will decrease.
>>I was expecting the steady state at something like 4 GB
>>( after a full vacuum and reindex ) + 10 % = 4.4 GB
>>I'm at 4.6 GB and increasing. I'll see how it will continue.
>>    
>>
>
>You probably want for the "experiment" to last more than a week.
>
>After all, it might actually be that with your usage patterns, that
>table would stabilize at 15% "overhead," and that might take a couple
>or three weeks.
>
>Unless it's clear that it's growing perilously quickly, just leave it
>alone so that there's actually some possibility of reaching an
>equilibrium.  Any time you "VACUUM FULL" it, that _destroys_ any
>experimental results or any noticeable patterns, and it guarantees
>that you'll see "seemingly perilous growth" for a while.
>
>And if the table is _TRULY_ growing "perilously quickly," then it is
>likely that you should add in some scheduled vacuums on the table.
>Not VACUUM FULLs; just plain VACUUMs.
>
>I revised cron scripts yet again today to do hourly and "4x/day"
>vacuums of certain tables in some of our systems where we know they
>need the attention.  I didn't schedule any VACUUM FULLs; it's
>unnecessary, and would lead directly to system outages, which is
>totally unacceptable.
>  
>

Chris, is this in addition to pg_autovacuum?  Or do you not use 
pg_autovacuum at all?, and if so why not?





view thread (16+ messages)  latest in thread

Message-ID: <421CD6F0.8010406@zeut.net>
Permalink:  ../421CD6F0.8010406@zeut.net/
Also on:    postgresql.org/message-id/421CD6F0.8010406@zeut.net

 · 

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-performance@postgresql.org
  Cc: matthew@zeut.net, cbbrowne@ca.afilias.info
  Subject: Re: is pg_autovacuum so effective ?
  In-Reply-To: <421CD6F0.8010406@zeut.net>

* 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