Re: [HACKERS] Explicit relation name in VACUUM VERBOSE log - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Explicit relation name in VACUUM VERBOSE log
Date
Msg-id 14199.1503585323@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Explicit relation name in VACUUM VERBOSE log  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [HACKERS] Explicit relation name in VACUUM VERBOSE log  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Michael Paquier wrote:
>> Hm. I am not sure what you have in mind here.

> I'm thinking that this data is useful to analyze as a stream of related
> events, rather than as individual data points.  Grepping logs in order to
> extract the numbers is lame and slow.

Yes.  And there is a bigger issue here, which is that the output of
VACUUM VERBOSE is meant to be sent to the client for *human* readability.
(As you noted, INFO-level messages don't normally go to the server log
in the first place, and that's not by accident.)  Repeating the full table
name in every line will be really annoying for that primary use-case.
I am not sure what we want to do to address Masahiko-san's use-case, but
ideally his workflow wouldn't involve log-scraping at all.  It definitely
shouldn't involve depending on INFO messages --- for one thing, what
happens when those get translated?
        regards, tom lane



pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Updating line length guidelines