postgres.git / summary / log / commit / refs

commit    e22fd217ec5b5b454febd5c1a1cc3c3f1c4e3a63
Author:   David Rowley <drowley@postgresql.org>
Date:     Tue Apr 12 21:17:17 2022 +0000
First released in: 15.0, 12.11, 13.7, 14.3

    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


 doc/src/sgml/ref/pg_rewind.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml
index d24584256e4..cdfacf70888 100644
--- a/doc/src/sgml/ref/pg_rewind.sgml
+++ b/doc/src/sgml/ref/pg_rewind.sgml
@@ -210,8 +210,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 on a production
+        the data directory corrupt.  Generally, this option is useful for
+        testing but should not be used on a production
         installation.
        </para>
       </listitem>


[parent: 87166d25a456]