Re: 3rd time is a charm.....right sibling is not next child crash.

On 6/8/10 12:56 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Jeff Amiel <jamiel(at)istreamimaging(dot)com> writes:
>> On a side note, I am 100% sure that autovacuum was disabled when I brought
>> the database back up after the core dump(s). However, minutes after
>> restarting, some of my larger tables started getting vacuumed by pgsql user.
>> Any way that a vacuum would kick off for a particular table (or series of
>> tables) even when autovacuum was off in the postgresql.conf?
>
> Anti-transaction-wraparound vacuums, perhaps?

I would hope not. :)
This is postgres 8.2.X. Autovacuum has been enabled forever (seemingly with
no errors)
Anything I can look for ? (I searched the logs for references to "must be
vacuumed within" but found nothing....)

SELECT datname, age(datfrozenxid) FROM pg_database;

postgres 178649703

prod 204588751

template1 178653277

template0 178653131