| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Chris Wilson <chris+google(at)qwirx(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: What does "[backends] should seldom or never need to wait for a write to occur" mean? |
| Date: | 2020-11-12 17:37:30 |
| Message-ID: | 20201112173730.GF25584@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Nov 12, 2020 at 05:25:30PM +0000, Chris Wilson wrote:
> Hi Bruce,
>
> Thanks, I absolutely agree that this documentation needs to explain properly
> how the bgwriter works. Your latest patch looks good, it significantly improves
> this section of the manual. I would just suggest changing "non-dirty" to
> "clean" in "When the number of non-dirty shared buffers appears to be
> insufficient", as this makes the language simpler and avoids introducing
> another new term (non-dirty, which means the same as clean).
OK, done. I wasn't sure 'clean' would be assumed to be non-dirty, but you
are right the language is clearer with 'clean'. (I was afraid 'clean'
would be assumed to be 'empty'.)
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| Attachment | Content-Type | Size |
|---|---|---|
| bgwriter.diff | text/x-diff | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-11-12 20:13:26 | Re: Missing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.html |
| Previous Message | Chris Wilson | 2020-11-12 17:25:30 | Re: What does "[backends] should seldom or never need to wait for a write to occur" mean? |