Maybe a good measure of how often the database needs to be vacuumed is how
often the administrators currently vacuum it?
For instance, if it's being vacuumed less than once a day, it may be
perfectly acceptable to vacuum it once early in the morning when nobody is
using it - assuming nobody uses it then, of course.
If the administrators have been using the product for a while, it may not be
too much of a problem to ask when the "slow times" are - you might be able
to just ask them. We do electronic billing, and I've found that the people
who know the most about slow times and such are those people, and the Tech
Support Queen.
Just a couple of thoughts...
Neil
-----Original Message-----
From: Rainer Mager [mailto:rmager@vgkk.com]
Sent: Thursday, July 13, 2000 5:47 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] vacuum
Hi all,
I'm sure many other people have faced this and I'm wondering what
solutions
were found.
We have a product that uses PostgreSQL as its database. Currently,
via a
web-based administration interface, we provide the administrators the
ability to vacuum their database whenever they wish to. We would prefer to
provide this functionality automatically such that they don't need to think
about it.
We could easily have the system vacuum once a day (or week or
whatever) but
we are concerned that the vacuum process will slow down the system while it
is being performed. This means that we would need to try to do some analysis
on the business of the system and then vacuum at a perceived slow time. This
sounds difficult.
What do other people do? How much of a hit is vacuum when the system
is
operating? Any other ideas?
Thanks in advance,
--Rainer
