Sounds like a good idea and i think i think more control of the autovacuum
process has been discussed here recently.
As to my initial problem, i eventually solved it. One of my colleagues was
using a full table lock despite denying it originally, this was causing the
problem. Took some tracking down as it the culprit statement always looked
like an update hence my original questions..
Autovacuum running again fine now and i've even tuned it down a bit as
suggested which was a new feature for me
Thanks for all your help.
JOHN
----- Original Message -----
From: "Rajesh Kumar Mallah" <mallah.rajesh@xxxxxxxxx>
To: "Tom Lane" <tgl@xxxxxxxxxxxxx>
Cc: "John Lister" <john.lister-ps@xxxxxxxxxxxxx>;
<pgsql-admin@xxxxxxxxxxxxxx>
Sent: Wednesday, February 11, 2009 3:37 PM
Subject: Re: controlling autovacuum during the day.
On Wed, Dec 17, 2008 at 7:17 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
"John Lister" <john.lister-ps@xxxxxxxxxxxxx> writes:
I'd like to use autovacuum to clean up the tables rather than schedule a
full vacuum with cron as it will be more selective/intelligent about
what
gets cleaned. But is it possible to stop it running during peak/office
hours?
No. Instead, set the vacuum cost parameters to make it run slow enough
to not interfere too much with your work.
is it a bad idea to have such a feature ?
i was going through ./src/backend/postmaster/autovacuum.c
looks like subroutine autovac_start can be modfied to
for the said feature. In case it does not have negative implication
can i submit a patch ?
regds
-- mallah.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
