From: Jerry Champlin <jchamplin@absolute-performance.com>
To: depesz@depesz.com
Cc: pgsql-performance@postgresql.org, Andrew Sullivan <ajs@commandprompt.com>
Subject: Re: Autovacuum does not stay turned off
Date: Tue, 26 Aug 2008 10:45:31 -0600
Message-ID: <48B4332B.4050207@absolute-performance.com> (raw)
In-Reply-To: <20080826161427.GA25880@depesz.com>
References: <48B420F4.5020406@absolute-performance.com>
<20080826161427.GA25880@depesz.com>
This makes sense. What queries can I run to see how close to the limit
we are? We need to determine if we should stop the process which
updates and inserts into this table until after the critical time this
afternoon when we can perform the required maintenance on this table.
hubert depesz lubaczewski wrote:
> On Tue, Aug 26, 2008 at 09:27:48AM -0600, Jerry Champlin wrote:
>
>> Does anyone know what will cause this bahavior for autovacuum?
>>
>
> http://www.postgresql.org/docs/current/interactive/runtime-config-autovacuum.html
> -> autovacuum_freeze_max_age
>
> depesz
>
>
Andrew Sullivan wrote:
> On Tue, Aug 26, 2008 at 09:27:48AM -0600, Jerry Champlin wrote:
>
>> Does anyone know what will cause this bahavior for autovacuum?
>>
>
> You're probably approaching the wraparound limit in some database.
>
> If you think you can't afford the overhead when users are accessing
> the system, when are you vacuuming?
>
> A
>
>
We are changing the table structure tonight. These two tables are very
highly updated. The goal is to use autovacuum but not have it take 10
days to run on a 13MM record table.
Thanks
-Jerry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jchamplin@absolute-performance.com, depesz@depesz.com, ajs@commandprompt.com
Subject: Re: Autovacuum does not stay turned off
In-Reply-To: <48B4332B.4050207@absolute-performance.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox