| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | chris+postgresql(at)qwirx(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-10-29 22:33:13 |
| Message-ID: | CAKFQuwb=gsfEq-HL+7Oh92dVdf2YZwYEtGv6KJXugfEWECYJag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Oct 29, 2020 at 3:24 PM PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/13/runtime-config-resource.html
> Description:
>
>
> https://www.postgresql.org/docs/13/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-BACKGROUND-WRITER
>
> says:
>
> "There is a separate server process called the background writer, whose
> function is to issue writes of “dirty” (new or modified) shared buffers. It
> writes shared buffers so server processes handling user queries seldom or
> never need to wait for a write to occur."
>
> It's not clear what "wait for a write to occur" means: a write() syscall or
> an fsync() syscall?
>
Probably neither...think more abstract/general.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryn Llewellyn | 2020-10-30 00:13:22 | Re: COPY statement: no list of the allowed values for "format_name" |
| Previous Message | David G. Johnston | 2020-10-29 22:29:15 | Re: COPY statement: no list of the allowed values for "format_name" |