| 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 16:54:12 |
| Message-ID: | 20201112165412.GC25584@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Nov 12, 2020 at 02:40:04PM +0000, Chris Wilson wrote:
> Hi Bruce,
>
> Thanks, yes I agree that that is much clearer. However when you say:
>
>
> When the percentage of dirty shared buffers is high, the background writer
> writes some of them to the file system...
>
>
> I haven't seen anything about a minimum percentage before the bgwriter kicks
> in, is that really the case? How is it configured?
Yes, I see your point. My language was not accurate, and it didn't
match the actual background writer tuning parameters below this text.
Here is an updated doc patch.
I agree this text should be as clear as possible because there is no way
to properly tune the background writer parameters unless we explain how
it works. It is good you noticed this.
--
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 | 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? |
| Previous Message | Chris Wilson | 2020-11-12 14:40:04 | Re: What does "[backends] should seldom or never need to wait for a write to occur" mean? |