manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <>
Subject Re: autovacuum
Date Tue, 19 Nov 2013 19:19:14 GMT
Hi Ronny,

Not sure if you ever got a reply to this question.

Basically, the recommendations for VACUUM were created on a much earlier
version of PostgreSQL.  The architecture of VACUUM may well have
changed/been improved since then.  What we were seeing in the past, though,
was that under the loads that ManifoldCF applied:
- autovacuum could not keep up
- overall performance of PostgreSQL degraded over time
- autovacuum stole cycles from ManifoldCF disproportional to the
alternative, which was VACUUM FULL.

Your mileage may vary, but if you learn anything new please post.


On Sat, Nov 9, 2013 at 3:48 PM, Ronny Heylen <>wrote:

> Turning autovacuum off as recommended in the manifoldcf optimization guide,
> I receive the message here after.
> Postgresql is version 9.3.
> Is it still applicable that we should vacuum ourselve everyday?
> Running autovacuum recommended
> Introduced in PostgreSQL 8.1, the autovacuum process which was previously
> implemented as an external service process is now integrated into the
> backend. It will run VACUUM automatically if a configurable amount of data
> has changed.
> Running VACUUM is mandatory on a PostgreSQL server to keep data consistent
> and the server performant. As a start, it is recommended to enable the
> autovacuum daemon by setting 'autovacuum', 'stats_start_collector' and
> 'stats_row_level' in postgresql.conf to 'on'.
> In PostgreSQL 8.3 and newer, autovacuum is enabled by default unless you
> turn off 'track_activities' or 'track_counts'.
> With a usually neglible performance penalty from the data change tracking,
> you will gain automatic VACUUM runs.
> To adjust autovacuum performance for individual needs, you might need to
> tune its settings using global parameters in postgresql.conf, or
> individually on each table; see the documentation.

View raw message