Hello community,
we are running a CRM system with Postgres database (version 8.3). To
organize handwritten contracts we save them scanned as LOBs. Normally
they are unlinked in case of deleting them. However we run a cron job
which does vacuumlo to get save that there is nothing in the
Alexander Strotmann a écrit :
[...]
we are running a CRM system with Postgres database (version 8.3). To
organize handwritten contracts we save them scanned as LOBs. Normally
they are unlinked in case of deleting them. However we run a cron job
which does vacuumlo to get save that there is
Hello Gurus,
I'm new to PG , running PG 8.3 on Linux and reading trough docs is
mentioned that in PG vers 8.3 an AUTO vacuum process has been
implemented which will run
full vacuum on all user and system tables + analyze and there is NO
need fro DBA to schedule a crontab job to run
Hello there,
Yes, the autovacuum is set on by default on the PG 8.3.
The vacuum is not full, to run a full vacuum you need to set a cron job;
better to run at the night.
I don't set autovacuum on the production databases, only in the Slony's
slave machines and in the developmente machine.
For
Rafael Domiciano escribió:
The vacuum is not full, to run a full vacuum you need to set a cron job;
better to run at the night.
Doing VACUUM FULL on crontab is rarely a good idea. If you find
yourself in a situation where you need VACUUM FULL, then you've not
tuned regular vacuum
On Fri, Oct 31, 2008 at 10:02 AM, Alvaro Herrera
[EMAIL PROTECTED] wrote:
Rafael Domiciano escribió:
The vacuum is not full, to run a full vacuum you need to set a cron job;
better to run at the night.
Doing VACUUM FULL on crontab is rarely a good idea. If you find
yourself in a situation
