summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2022-04-13 09:17:56 +1200
committerDavid Rowley <drowley@postgresql.org>2022-04-13 09:17:56 +1200
commitaf3e3a9b4f525c93c10a29bcaeadc179bed1cca1 (patch)
treec61b85e4b26aca48c29316028f3a31d1bba2bad8
parent989d3e4a2957d9ffbcc57414941b1946d4beece8 (diff)
downloadpostgresql-af3e3a9b4f525c93c10a29bcaeadc179bed1cca1.tar.gz
Docs: avoid confusing use of the word "synchronized"
It's misleading to call the data directory the "synchronized data directory" when discussing a crash scenario when using pg_rewind's --no-sync option. Here we just remove the word "synchronized" to avoid any possible confusion. Author: Justin Pryzby Discussion: https://postgr.es/m/20220411020336.GB26620@telsasoft.com Backpatch-through: 12, where --no-sync was added
-rw-r--r--doc/src/sgml/ref/pg_rewind.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml
index 58addfcb96..272bd113b9 100644
--- a/doc/src/sgml/ref/pg_rewind.sgml
+++ b/doc/src/sgml/ref/pg_rewind.sgml
@@ -182,8 +182,8 @@ PostgreSQL documentation
to be written safely to disk. This option causes
<command>pg_rewind</command> to return without waiting, which is
faster, but means that a subsequent operating system crash can leave
- the synchronized data directory corrupt. Generally, this option is
- useful for testing but should not be used when creating a production
+ the data directory corrupt. Generally, this option is useful for
+ testing but should not be used when creating a production
installation.
</para>
</listitem>