From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: chris+postgresql@qwirx.com
Subject: What does "[backends] should seldom or never need to wait for a write to occur" mean?
Date: Thu, 29 Oct 2020 18:20:20 +0000
Message-ID: <160399562040.7809.7335281028960123489@wrigleys.postgresql.org> (raw)
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-W...
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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, chris+postgresql@qwirx.com
Subject: Re: What does "[backends] should seldom or never need to wait for a write to occur" mean?
In-Reply-To: <160399562040.7809.7335281028960123489@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox