Postgres Pro
Downloads
Home   >   mailing lists

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

From PG Doc comments form
Subject What does "[backends] should seldom or never need to wait for a write to occur" mean?
Date
Msg-id 160399562040.7809.7335281028960123489@wrigleys.postgresql.org
Whole thread Raw
Responses Re: What does "[backends] should seldom or never need to wait for a write to occur" mean?  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: What does "[backends] should seldom or never need to wait for a write to occur" mean?  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-docs
Tree view 
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?

pgsql-docs by date:

Previous
From: PG Doc comments form
Date:
Subject: COPY statement: no list of the allowed values for "format_name"
Next
From: "David G. Johnston"
Date:
Subject: Re: COPY statement: no list of the allowed values for "format_name"