From: Shoaib Mir <shoaibmir@gmail.com>
To: Bill Moran <wmoran@collaborativefusion.com>
Cc: Gauri Kanekar <meetgaurikanekar@gmail.com>
Cc: Michael Glaesemann <grzm@seespotcode.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Vacuum v/s Autovacuum
Date: Thu, 18 Jan 2007 19:14:25 +0500
Message-ID: <bf54be870701180614k2cc40403pe7665e7759cbe629@mail.gmail.com> (raw)
In-Reply-To: <20070118090528.eec9e398.wmoran@collaborativefusion.com>
References: <7e4ba9550701180524h5ebe3390v73292cb91aed89fa@mail.gmail.com>
<A9D4D3AB-FB33-47BF-A354-4064DF38293C@seespotcode.net>
<7e4ba9550701180546u38609442ic5103a834f7b7d0d@mail.gmail.com>
<20070118090528.eec9e398.wmoran@collaborativefusion.com>
You will need to properly tune the thresholds for VACUUM and ANALYZE in case
of autovacuuming process, so that you do not need to increase the
max_fsm_pages oftenly...
-------------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/18/07, Bill Moran <wmoran@collaborativefusion.com> wrote:
>
> In response to "Gauri Kanekar" <meetgaurikanekar@gmail.com>:
> > On 1/18/07, Michael Glaesemann <grzm@seespotcode.net> wrote:
> > >
> > > On Jan 18, 2007, at 22:24 , Gauri Kanekar wrote:
> > >
> > > > is autovacuum similar to vacuum full analyse verbose.
> > >
> > > http://www.postgresql.org/docs/8.2/interactive/routine-
> > > vacuuming.html#AUTOVACUUM
> > >
> > > Apparently, no FULL, no VERBOSE (which is only really useful if you
> > > want to see the results, not for routine maintenance).
>
> [please don't top-post]
>
> Actually, you can raise the debugging level in PostgreSQL and get
> something
> similar to VERBOSE. The only problem is that it also increases the amount
> of logging that occurs with everything.
>
> > We have autovacuum ON , but still postgres server warns to
> > increas max_fsm_pages value.
> >
> > Do autovacuum release space after it is over?
>
> Yes.
>
> If you're still getting warnings about max_fsm_pages while autovac is
> running, you need to do one of two things:
> 1) Increase max_fsm_pages
> 2) Adjust autovacuum's settings so it vacuums more often.
>
> Depending on this, you may also need to temporarily adjust max_fsm_pages,
> then manually vacuum -- you may then find that autovacuum can keep
> everything
> clean with lower settings of max_fsm_pages.
>
> Overall, the best settings for 1 and 2 depend on the nature of your
> workload, and simulation and monitoring will be required to find the
> best values. I feel that the docs on this are very good. If the
> amount of data that changes between runs of autovacuum is greater
> than max_fsm_pages, then vacuum will be unable to reclaim all the
> space.
>
> --
> Bill Moran
> Collaborative Fusion Inc.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
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: shoaibmir@gmail.com, wmoran@collaborativefusion.com, meetgaurikanekar@gmail.com, grzm@seespotcode.net
Subject: Re: Vacuum v/s Autovacuum
In-Reply-To: <bf54be870701180614k2cc40403pe7665e7759cbe629@mail.gmail.com>
* 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