Re: [HACKERS] Additional logging for VACUUM and ANALYZE - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Additional logging for VACUUM and ANALYZE
Date
Msg-id CA+TgmobH17W=WdduhXJhxdwHAeTazNp7MDP=k0p=2w1nuSSruw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Additional logging for VACUUM and ANALYZE  ("Bossart, Nathan" <bossartn@amazon.com>)
Responses Re: [HACKERS] Additional logging for VACUUM and ANALYZE
List pgsql-hackers
On Fri, Dec 1, 2017 at 11:29 AM, Bossart, Nathan <bossartn@amazon.com> wrote:
> Thanks for the review, Robert.  I've attached a new version that
> addresses your feedback.

Thanks.  I think this looks fine now, except that (1) it needs a
pgindent run and (2) I vote for putting the test case back.  Michael
thought the test case was too much because this is so obscure, but I
think that's exactly why it needs a test case.  Otherwise, somebody a
few years from now may not even be able to figure out how to hit this
message, and if it gets broken, we won't know.  This code seems to be
fairly easy to break in subtle ways, so I think more test coverage is
good.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Custom compression methods
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Transaction control in procedures