From: Scott Marlowe <scott.marlowe@gmail.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Rick <richard.branton@ca.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: autovacuum strategy / parameters
Date: Sat, 1 May 2010 10:13:25 -0600
Message-ID: <y2gdcc563d11005010913w3a24a73dl9e6c5e0ae174f730@mail.gmail.com> (raw)
In-Reply-To: <4BDB5ECE.4010607@agliodbs.com>
References: <c2d2b6cf-895f-4a4b-aa8b-3adaac33c794@z3g2000yqz.googlegroups.com>
<y2g603c8f071004221155h3874a3c0ybbe2c790e3c1bf80@mail.gmail.com>
<65d9d15d-41d2-4bfa-8cc3-6148b4fb9022@z3g2000yqz.googlegroups.com>
<h2o603c8f071004271755v3e56a408hbd23b5c355058aa@mail.gmail.com>
<4BDB5ECE.4010607@agliodbs.com>
On Fri, Apr 30, 2010 at 4:50 PM, Josh Berkus <josh@agliodbs.com> wrote:
> Which is the opposite of my experience; currently we have several
> clients who have issues which required more-frequent analyzes on
> specific tables. Before 8.4, vacuuming more frequently, especially on
> large tables, was very costly; vacuum takes a lot of I/O and CPU. Even
> with 8.4 it's not something you want to increase without thinking about
> the tradeoff
Actually I would think that statement would be be that before 8.3
vacuum was much more expensive. The changes to vacuum for 8.4 mostly
had to do with moving FSM to disk, making seldom vacuumed tables
easier to keep track of, and making autovac work better in the
presence of long running transactions. The ability to tune IO load
etc was basically unchanged in 8.4.
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-performance@postgresql.org
Cc: scott.marlowe@gmail.com, josh@agliodbs.com, robertmhaas@gmail.com, richard.branton@ca.com
Subject: Re: autovacuum strategy / parameters
In-Reply-To: <y2gdcc563d11005010913w3a24a73dl9e6c5e0ae174f730@mail.gmail.com>
References: <c2d2b6cf-895f-4a4b-aa8b-3adaac33c794@z3g2000yqz.googlegroups.com> <y2g603c8f071004221155h3874a3c0ybbe2c790e3c1bf80@mail.gmail.com> <65d9d15d-41d2-4bfa-8cc3-6148b4fb9022@z3g2000yqz.googlegroups.com> <h2o603c8f071004271755v3e56a408hbd23b5c355058aa@mail.gmail.com> <4BDB5ECE.4010607@agliodbs.com> <y2gdcc563d11005010913w3a24a73dl9e6c5e0ae174f730@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