From: | Natalie Wenz <nataliewenz(at)ebureau(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | autovacuum to prevent wraparound question |
Date: | 2014-12-08 22:28:19 |
Message-ID: | D58D0958-EE59-4D71-A335-2C29603E6EDF@ebureau.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Khangelani Gama | 2014-12-09 11:18:43 | Group by clause - Postgres 9.2.4 |
Previous Message | lst_hoe02 | 2014-12-08 14:00:29 | Re: Postgres 9.1.8 - Out of memory: postgres killed after changing "checkoint_completion_target" |