Re: What does "[backends] should seldom or never need to wait for a write to occur" mean? - Mailing list pgsql-docs

From Bruce Momjian
Subject Re: What does "[backends] should seldom or never need to wait for a write to occur" mean?
Date
Msg-id 20201111232417.GH25840@momjian.us
Whole thread Raw
In response to Re: What does "[backends] should seldom or never need to wait for a write to occur" mean?  (Chris Wilson <chris+google@qwirx.com>)
Responses Re: What does "[backends] should seldom or never need to wait for a write to occur" mean?  (Chris Wilson <chris+google@qwirx.com>)
List pgsql-docs
On Wed, Nov 11, 2020 at 11:29:09AM +0000, Chris Wilson wrote:
> I still believe that my original proposed change, to "This reduces the chances
> that a backend needing an empty buffer must [itself] write a dirty one back to
> disk before evicting it" (with one extra word added), resolves the ambiguity
> and also more clearly and directly focuses it on what the bgwriter does and
> why, making it better documentation. It might be incorrect if my understanding
> is incorrect - is it?

You make some very good points.  Here is an updated patch.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee


Attachment

pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Addition to content
Next
From: Fujii Masao
Date:
Subject: doc: index items for pg_stat_progress_xxx views