The return of the auto-vacuum

From: "Nestor A(dot) Diaz" <nestor(at)tiendalinux(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: The return of the auto-vacuum
Date: 2015-02-11 15:49:07
Message-ID: 54DB79F3.9050202@tiendalinux.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello Everybody,

This is the scenario:

I have a postgres 8.4, debian packages installed from pgdg repository
and version equal to: 8.4.21-1.pgdg70+1

I have a GPS database that insert about 4 million records on some tables
every week, the database is partitioned per week, I do a manual vacuum
every week and when we start the week then we 'vacuum analyze' the last
week tables.

However sometimes we have autovacuum running on older tables and I don't
know why, something like this:

autovacuum: VACUUM partitions.device_event_2015w05 (to prevent wraparound)

Those tables are almost read only, they are just involved in select
queries, but the system sometimes autovacuum them.

Any guess on why is the autovacuum daemon starting the process on those
tables ? It doesn't matter if they have been vacuumend before and
nothing have changed on those tables ?

Sorry, I still don't understand how the 'prevent wraparound' works, I
thought that 'vacuum to prevent wraparound' only got fired on tables
that were highly modified.

Thanks.

--
Nestor.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-02-11 16:07:21 Re: The return of the auto-vacuum
Previous Message Adrian Klaver 2015-02-11 15:26:32 Re: Cluster seems broken after pg_basebackup