Re: Logging idle checkpoints

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: alvherre(at)alvh(dot)no-ip(dot)org
Cc: sfrost(at)snowman(dot)net, michael(dot)paquier(at)gmail(dot)com, vik(dot)fearing(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Logging idle checkpoints
Date: 2017-10-05 12:02:41
Message-ID: 20171005.210241.141024939.horiguchi.kyotaro@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 5 Oct 2017 13:41:42 +0200, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote in <20171005114142(dot)dupjeqe2cnplhgkx(at)alvherre(dot)pgsql>
> Kyotaro HORIGUCHI wrote:
>
> > # This reminded me of a concern. I'd like to count vacuums that
> > # are required but skipped by lock-failure, or killed by other
> > # backend.
>
> We clearly need to improve the stats and logs related to vacuuming work
> executed, both by autovacuum and manually invoked. One other item I
> have in my head is to report numbers related to the truncation phase of
> a vacuum run, since in some cases it causes horrible and hard to
> diagnose problems. (Also, add an reloption to stop vacuum from doing
> the truncation phase at all -- for some usage patterns that is a serious
> problem.)
>
> However, please do open a new thread about it.

Thanks! Will do after a bit time of organization of the thougts.

reagareds,

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-10-05 12:38:00 Re: parallelize queries containing initplans
Previous Message Alvaro Herrera 2017-10-05 11:41:42 Re: Logging idle checkpoints