From: Natalie Wenz <nataliewenz@ebureau.com>
To: pgsql-admin@postgresql.org
Subject: autovacuum to prevent wraparound question
Date: Mon, 8 Dec 2014 16:28:19 -0600
Message-ID: <D58D0958-EE59-4D71-A335-2C29603E6EDF@ebureau.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Does the auto vacuum process scan the whole database every time it runs (when triggered to prevent wraparound), or is it able to skip pages for which every row has already been frozen?
We have a large database that consists primarily of two large tables that receive a lot of insert records, but no rows are ever deleted or changed. Can we expect the autovacuum to always take longer and longer as those tables grow, scanning every row every time it is triggered to prevent wraparound, or is the vacuumer optimized to skip the parts that have already been frozen?
Thanks,
Natalie=
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: nataliewenz@ebureau.com
Subject: Re: autovacuum to prevent wraparound question
In-Reply-To: <D58D0958-EE59-4D71-A335-2C29603E6EDF@ebureau.com>
References: <D58D0958-EE59-4D71-A335-2C29603E6EDF@ebureau.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