How often depends on how busy your db is. But I'd recommend running it at
least once a day.
Vacuum analyze updates the statistics that the db uses to determine various
query plans, so I'd always run it as vacuum analyze, rather than just
vacuum.
Leave postmater running when you run it. There's no need to take it offline.
Consider running it as a cron job.
Tim
----- Original Message -----
From: "Peter Peltonen" <peter.peltonen@fivetec.com>
To: <pgsql-general@postgresql.org>
Sent: Wednesday, February 27, 2002 7:12 AM
Subject: [GENERAL] About vacuuming
> Questions regarding PostgreSQL 7.1.3 (if things are different with 7.2 I'd
> like to know that too :)
>
> How often one should vacuum his db?
>
> Is vacuum --analyze for just providing information or does it somehow
> store it's info for postgresql's use (in other words: should I run it too,
> and if so, should I do it before or after the real vacuum?).
>
> Should postmaster be running or not when vacuuming?
>
> Regards,
> Peter
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
