Re: why is autovacuum still ongoing even if set to off ?

The insertion rate is ~250 records / second, quite uniformly spread in
time over ~3000 tables. To reach 2^31 something like 100 days are needed
and the cluster is less than 10 days old. And we do vacuuming :) So as
far as I understand, the wraparound shouldn't happen. In fact before 8.4
we ran for 3 years and never had any problems, so with a fresh
installation there should be even less...

Anyway, if for whatever reason autovacuum kicks in, it should at least
sleep a while between moving to the next table and then it wouldn't be a
major issue. But the configuration option set doesn't seem to include
such an option.

Cheers,

.costin

Scott Marlowe wrote:
> On Thu, Jul 30, 2009 at 2:52 PM, Costin Grigoras<costing(at)gmail(dot)com> wrote:
>
>> Hi,
>>
>> I'm running 8.4 and I've tried to disable autovacuum since the vacuuming is
>> taken care internally in the code. The same was true with the previous
>> version (8.0 to 8.3) and there was never any problem. However now in 8.4 the
>> "off" setting seems to be ignored even if "track_counts = off" and huge
>> naptime and thresholds are set. For example this is in the logs:
>>
>
> The only thing I can think of is the automatic kickoff of autovacuum
> to prevent transaction wraparound.
>