From: Brad Nicholson <bnichols@ca.afilias.info>
To: pgsql-performance@postgresql.org
Subject: Re: Memory usage - indexes
Date: Fri, 24 Sep 2010 14:34:06 -0400
Message-ID: <4C9CEF1E.6000903@ca.afilias.info> (raw)
In-Reply-To: <AANLkTikWhZRZvJGJyNb03KJ3oqmMNju0FNtHxMb5bact@mail.gmail.com>
References: <AANLkTimd0Y7KhnwkSXz4FYjsxC8ocDeRRH=PXvU1a3vv@mail.gmail.com>
<865426.21884.qm@web39701.mail.mud.yahoo.com>
<AANLkTinK6jGN5+q=1FYjD8EkTJTB24rc-dd3_YnNgg=5@mail.gmail.com>
<4C9CDCDD.8000603@ca.afilias.info>
<AANLkTikWhZRZvJGJyNb03KJ3oqmMNju0FNtHxMb5bact@mail.gmail.com>
On 10-09-24 01:41 PM, Tobias Brox wrote:
> What do you mean, that you could run regular vacuum less frequently,
> or that the regular vacuum would go faster?
It means that vacuums ran less frequently. With cron triggered vacuums,
we estimated when tables needed to be vacuumed, and vacuumed them
accordingly. Because of unpredictable shifts in activity, we scheduled
the vacuums to happen more often than needed.
With autovacuum, we vacuum some of our large tables far less
frequently. We have a few large tables that used to get vacuumed every
other day that now get vacuumed once or twice a month.
The vacuums themselves take longer now as we use the vacuum cost delay
to control the IO. That wasn't an option for us when we did manual
vacuums as that was in 8.1 when vacuums were still treated as long
running transactions. Stretching a vacuum out to a few hours prior to
8.2 would bloat other tables.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
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: bnichols@ca.afilias.info
Subject: Re: Memory usage - indexes
In-Reply-To: <4C9CEF1E.6000903@ca.afilias.info>
* 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