Re: 3rd time is a charm.....right sibling is not next child crash. - Mailing list pgsql-general

From Tom Lane
Subject Re: 3rd time is a charm.....right sibling is not next child crash.
Date
Msg-id 7550.1276019770@sss.pgh.pa.us
Whole thread Raw
In response to Re: 3rd time is a charm.....right sibling is not next child crash.  (Jeff Amiel <jamiel@istreamimaging.com>)
Responses Re: 3rd time is a charm.....right sibling is not next child crash.  (Jeff Amiel <jamiel@istreamimaging.com>)
List pgsql-general
Jeff Amiel <jamiel@istreamimaging.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?

            regards, tom lane

pgsql-general by date:

Previous
From: Andy Colson
Date:
Subject: Re: Some insight on the proper SQL would be appreciated
Next
From: uaca man
Date:
Subject: Re: Queues Problem