Re: Template0 datfrozenxid age is 160million and progressing

From: Rijo Roy <rjo_roy(at)yahoo(dot)com>
To: "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "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 14:31:11
Message-ID: 1878935582.502633.1533133871925@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I agree.. But unfortunately it is the business call and we cannot alter it.. I am planning to convince them by keeping autovacuum_analyze_threshold to a high value so that auto analyse will not kick in very often leaving the autovacuum to do its job.. Please advise. 
Thanks, Rijo Roy 
Sent from Yahoo Mail on Android

On Wed, 1 Aug 2018 at 7:54 pm, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: Rijo Roy <rjo_roy(at)yahoo(dot)com> writes:
> Thanks for the advice. Autovacuum is disabled in the environment and I cannot take a call on enabling it back. I can only run manual vacuum on the database as the dev team fears autoanalyze changing the query performance. Do you still think we don't need to take any actions. 

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.

            regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2018-08-01 14:39:01 Re: Settings for fast restores
Previous Message Tom Lane 2018-08-01 14:24:24 Re: Template0 datfrozenxid age is 160million and progressing