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

From David G. Johnston
Subject Re: What does "[backends] should seldom or never need to wait for a write to occur" mean?
Date
Msg-id CAKFQuwb=gsfEq-HL+7Oh92dVdf2YZwYEtGv6KJXugfEWECYJag@mail.gmail.com
Whole thread Raw
In response to What does "[backends] should seldom or never need to wait for a write to occur" mean?  (PG Doc comments form <noreply@postgresql.org>)
List pgsql-docs
On Thu, Oct 29, 2020 at 3:24 PM PG Doc comments form <noreply@postgresql.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.

pgsql-docs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: COPY statement: no list of the allowed values for "format_name"
Next
From: Bryn Llewellyn
Date:
Subject: Re: COPY statement: no list of the allowed values for "format_name"