From: David Rowley Date: Tue, 12 Apr 2022 21:17:56 +0000 (+1200) Subject: Docs: avoid confusing use of the word "synchronized" X-Git-Tag: REL_12_11~34 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=af3e3a9b4f525c93c10a29bcaeadc179bed1cca1;p=thirdparty%2Fpostgresql.git 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 --- diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index 58addfcb96d..272bd113b9a 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 pg_rewind 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.