From: Josh Berkus <josh@agliodbs.com>
To: Robert Treat <xzilla@users.sourceforge.net>
To: Clarence Gardner <clarence@silcom.com>
Cc: Oleg Lebedev <oleg.lebedev@waterford.org>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: slow query
Date: Mon, 24 Feb 2003 10:45:20 -0800
Message-ID: <200302241045.20856.josh@agliodbs.com> (raw)
In-Reply-To: <1046111434.1014.165.camel@camel>
References: <Pine.LNX.4.44.0302240925360.25665-100000@liberty.sba2.netlojix.net>
<1046111434.1014.165.camel@camel>
Robert,
> Actually if you are vacuuming frequently enough, it can (and should*)
> obviate a vacuum full. Be aware that frequently enough might mean really
> frequent, for instance I have several tables in my database that update
> every row within a 15 minute timeframe, so I run a "lazy" vacuum on
> these tables every 10 minutes. This allows postgresql to reuse the space
> for these tables almost continuously so I never have to vacuum full
> them.
This would assume absolutely perfect FSM settings, and that the DB never gets
thrown off by unexpected loads. I have never been so fortunate as to work
with such a database. However, I agree that good FSM tuning and frequent
regular VACUUMs can greatly extend the period required for running FULL.
I have not found, though, that this does anything to prevent the need for
REINDEX on frequently-updated tables. How about you, Robert?
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, xzilla@users.sourceforge.net, clarence@silcom.com, oleg.lebedev@waterford.org
Subject: Re: slow query
In-Reply-To: <200302241045.20856.josh@agliodbs.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