Re: Template0 datfrozenxid age is 160million and progressing

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "rjo_roy(at)yahoo(dot)com" <rjo_roy(at)yahoo(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Template0 datfrozenxid age is 160million and progressing
Date: 2018-08-01 16:12:27
Message-ID: 20180801161227.hmblujrvstqsubow@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2018-08-01 12:07:16 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2018-08-01 10:24:24 -0400, Tom Lane wrote:
> >> IMO, the action you need to take is enabling autovacuum. We've
> >> seen many many people go down the path you are taking, and it's
> >> generally led to no good in the end. Manual vacuuming tends
> >> to miss stuff, and it cannot react adequately to activity spikes.
>
> > But it shouldn't matter here, autovacuum will start regardless, no?
>
> Sure, once it decides that emergency anti-wraparound vacuuming is
> necessary. I really doubt the OP wants that to happen; it's the
> exact opposite of non-intrusive.

That's solely what would trigger it were autovacuum enabled, too? I've
complained about "emergency anti-wraparound" beeing anything but
emergency (they're largely unavoidable unless you manually script it),
but they're what happen once autovacuum_freeze_max_age is reached, and
that's the only trigger for vacuuming old relations independent of other
activity?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2018-08-01 16:20:15 Re: Template0 datfrozenxid age is 160million and progressing
Previous Message Tom Lane 2018-08-01 16:07:16 Re: Template0 datfrozenxid age is 160million and progressing