aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2023-11-09 17:51:19 -0500
committerBruce Momjian <bruce@momjian.us>2023-11-09 17:51:19 -0500
commit5ba1ac99a8d8623604d3152be8fd9a201ba5240b (patch)
tree36ee7905bfb8080aca8d5f142f9df7b802f890ce
parent80e278e436a7ad5cb4724d8b8ef39e79e4c3f5e6 (diff)
downloadpostgresql-5ba1ac99a8d8623604d3152be8fd9a201ba5240b.tar.gz
postgresql-5ba1ac99a8d8623604d3152be8fd9a201ba5240b.zip
doc: fix wording describing the checkpoint_flush_after GUC
Reported-by: Evan Macbeth Discussion: https://postgr.es/m/155208475619.1380.12815553062985622271@wrigleys.postgresql.org Backpatch-through: master
-rw-r--r--doc/src/sgml/wal.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 4aad0e1a075..184404c6c58 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -602,7 +602,7 @@
<para>
On Linux and POSIX platforms <xref linkend="guc-checkpoint-flush-after"/>
- allows to force the OS that pages written by the checkpoint should be
+ allows you to force OS pages written by the checkpoint to be
flushed to disk after a configurable number of bytes. Otherwise, these
pages may be kept in the OS's page cache, inducing a stall when
<literal>fsync</literal> is issued at the end of a checkpoint. This setting will