| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: log_autovacuum_min_duration doesn't log VACUUMs |
| Date: | 2017-03-04 05:42:14 |
| Message-ID: | CA+TgmoYB7MGNEth5opiSrOb-rjT50joB+oFE5VCrH_7ZtYbz2A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 1, 2017 at 11:00 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>> Because there are already various tools available to log activity of
>> session processes, but there are no other ways to log the activity of
>> autovacuum. Why are the existing settings not sufficient for this
>> purpose?
>
> I've pretty often been annoyed that the information provided by 'VACUUM
> VERBOSE' and the information provided by log_autovacuum_min_duration are so
> drastically different from each other. It would be pretty nice to have some
> way to get the same information for both operations in the same format,
> although I don't know if this proposal is the best way of accomplishing it.
Well said! I actually quite agree with the goal of making it possible
to get that reporting for manual VACUUMs. I just disagree with the
idea of tying it into this particular GUC.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-03-04 05:43:35 | Re: Patch: Optimize memory allocation in function 'bringetbitmap' |
| Previous Message | Robert Haas | 2017-03-04 05:39:40 | Re: Performance degradation in TPC-H Q18 |