Re: Documentation about pg_stat_bgwriter

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Documentation about pg_stat_bgwriter
Date: 2017-05-19 00:48:44
Message-ID: 343d4cdb-e25d-867d-2830-6502eca4df5c@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5/10/17 04:38, Kyotaro HORIGUCHI wrote:
> Hi. While I read the documentation I found the following
> description about some columns in pg_stat_bgwriter.
>
> https://www.postgresql.org/docs/devel/static/monitoring-stats.html#pg-stat-bgwriter-view
>
> This table shows cluster-global values, not per-backend values.
>
>> maxwritten_clean:
>> Number of times the background writer stopped a cleaning scan
>> because it had written too many buffers
>> buffers_backend:
>> Number of buffers written directly by a backend
>> buffers_backend_fsync:
>> Number of times a backend had to execute its own fsync call
>> (normally the background writer handles those even when the
>> backend does its own write)
> Since the values are the summary in a cluster, the 'a backend's
> in the last two seems wrong *to me*. I suppose the 'a backend'
> should be just 'backends' or 'backends other than the background
> writer' (This seems a bit verbose.).

The text looks correct to me as it currently stands. Your alternative
phrasings are also correct. But there is no need to change this, I think.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-05-19 00:53:26 Re: NOT NULL constraints on range partition key columns
Previous Message Peter Eisentraut 2017-05-19 00:30:17 fix for table syncing with different column order