From: | "Mikko Partio" <mpartio(at)gmail(dot)com> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Stray autovacuum daemon |
Date: | 2008-02-22 18:15:31 |
Message-ID: | 2ca799770802221015o7d4786f4v46467b379781d7c8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, Feb 22, 2008 at 7:01 PM, Mikko Partio <mpartio(at)gmail(dot)com> wrote:
>
>
> On Fri, Feb 22, 2008 at 5:44 PM, Alvaro Herrera <
> alvherre(at)commandprompt(dot)com> wrote:
>
> > Mikko Partio escribió:
> >
> > > Now, the problem is that I cannot turn autovacuum off! I have tried to
> > set
> > > autovacuum = off at postgresql.conf with no avail. I have also tried
> > to
> > > disable the vacuum by inserting rows to pg_autovacuum but still the
> > vacuum
> > > processes just pop up. What's even more weird is that autovacuum is
> > > vacuuming the same tables over and over. No sign of xid wraparound
> > issues
> > > show in the logs. How can I stop autovacuum without restarting the
> > database
> > > instance?
> >
> > If your database is in danger of Xid wraparound, autovacuum will run on
> > it no matter what you do. Check pg_class.relfrozenxid and
> > pg_database.datfrozenxid, and the current Xid counter (from
> > pg_controldata I think). Also take a look at the description of the
> > autovacuum_min_freeze_age param (or was it max_freeze_age? I forget).
> >
>
>
I think I may have found the problem, the import uses a temporary table
which I guess autovacuum can not handle? Manually vacuuming it changed the
relfrozenxids of other tables dramatically.
Regards
Mikko
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-02-22 18:16:59 | Re: server process (PID ) was terminated by signal 29 |
Previous Message | Mikko Partio | 2008-02-22 17:01:12 | Re: Stray autovacuum daemon |