| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| 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 11:41:42 |
| Message-ID: | 20171005114142.dupjeqe2cnplhgkx@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2017-10-05 12:02:41 | Re: Logging idle checkpoints |
| Previous Message | Alvaro Herrera | 2017-10-05 11:35:51 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |