Re: Cron-job for checking up on pg_autovacuum

From: Robert Creager <Robert_Creager(at)LogicalChaos(dot)org>
To: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
Cc: Markus Wollny <Markus(dot)Wollny(at)computec(dot)de>, pgsql-general(at)postgresql(dot)org
Subject: Re: Cron-job for checking up on pg_autovacuum
Date: 2003-11-30 05:12:54
Message-ID: 20031129221254.7e41ddc6.Robert_Creager@LogicalChaos.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

When grilled further on (Tue, 25 Nov 2003 11:19:32 -0500),
"Matthew T. O'Connor" <matthew(at)zeut(dot)net> confessed:

> I know I heard from at least one person who said they were running it
> from there inittab with respawn, which seems like overkill.

Nah, it works great (it was me). I just had an unclean shutdown/reboot, and
pg_autovacuum couldn't connect on start because PGSQL was coming up. inittab
took note of the quick respawning and put a 5 minute delay in there. And I got
to ignore it.

Also works great when PGSQL is down for any reason. You don't have to worry
about stopping/starting pg_autovacuum...

Overkill is a good thing! It keeps stuff working ;-)

Cheers,
Rob

my /etc/inittab line (Mandrake 9.1 system)

vac:235:respawn:su - postgres -c "/usr/local/pgsql/bin/pg_autovacuum -d 0"

--
22:06:18 up 2 days, 4:12, 1 user, load average: 2.11, 2.15, 2.17

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2003-11-30 05:14:24 Re: patch for pg_autovacuum
Previous Message Joe Conway 2003-11-30 05:08:53 export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)