From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | 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-01 17:30:32 |
Message-ID: | CAMkU=1zUZjwSomv-puy9fMMgY50t2T7Wh5L7dp3evZJVYEvrxQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 1, 2017 at 6:43 AM, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 2/10/17 03:38, Simon Riggs wrote:
> > I guess its fairly obvious in the title, but
> > log_autovacuum_min_duration doesn't log VACUUMs only autovacuums.
> >
> > What isn't obvious is why that restruction is useful.
>
> 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.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2017-03-01 17:34:05 | Re: SQL/JSON in PostgreSQL |
Previous Message | David Steele | 2017-03-01 17:26:42 | Re: pg_dump, pg_dumpall and data durability |