Still recommending daily vacuum...

From: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Still recommending daily vacuum...
Date: 2007-07-02 21:52:22
Message-ID: 20070702215222.GS85497@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

From
http://developer.postgresql.org/pgdocs/postgres/routine-vacuuming.html :

"Recommended practice for most sites is to schedule a database-wide
VACUUM once a day at a low-usage time of day, supplemented by more
frequent vacuuming of heavily-updated tables if necessary. (Some
installations with extremely high update rates vacuum their busiest
tables as often as once every few minutes.) If you have multiple
databases in a cluster, don't forget to VACUUM each one; the program
vacuumdb might be helpful."

Do we still want that to be our formal recommendation? ISTM it would be
more logical to recommend a combination of autovac, daily vacuumdb -a if
you can afford it and have a quiet period, and frequent manual vacuuming
of things like web session tables.

I'm happy to come up with a patch, but I figure there should be
consensus first...
--
Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-07-03 00:46:34 Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL
Previous Message Robert Treat 2007-07-02 21:23:02 Re: [COMMITTERS] pgsql: Fix PGXS conventions so that extensions can be built against

Browse pgsql-patches by date

  From Date Subject
Next Message Magnus Hagander 2007-07-02 22:00:18 Re: pg_ctl -w (wait) option on Windows
Previous Message Tom Lane 2007-07-02 20:57:22 Re: SPI-header-files safe for C++-compiler