| 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-16 18:14:05 |
| Message-ID: | 20201116181405.GE22426@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Nov 12, 2020 at 12:37:30PM -0500, Bruce Momjian wrote:
> 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'.)
Patch applied to all supported versions.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2020-11-16 20:05:43 | timed messages |
| Previous Message | Fujii Masao | 2020-11-16 15:26:29 | doc: cosmetic changes in index items |