Re: WAL usage calculation patch - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: WAL usage calculation patch
Date
Msg-id 96013912-6742-be14-dca4-6e8394cc0541@2ndquadrant.com
Whole thread Raw
In response to Re: WAL usage calculation patch  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: WAL usage calculation patch  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 2020-04-14 05:57, Amit Kapila wrote:
> Peter E, others, any suggestions on how to move forward?  I think here
> we should follow the rule "follow the style of nearby code" which in
> this case would be to have one space after each field as we would like
> it to be closer to the "Buffers" format.  It would be good if we have
> a unified format among all Explain stuff but we might not want to
> change the existing things and even if we want to do that it might be
> a broader/bigger change and we should do that as a PG14 change.  What
> do you think?

If looks like shortening to fpw= and using one space is the easiest way 
to solve this issue.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Autovacuum on partitioned table (autoanalyze)
Next
From: Tom Lane
Date:
Subject: Re: Support for DATETIMEOFFSET