diff options
| author | David Rowley | 2022-04-12 21:15:02 +0000 |
|---|---|---|
| committer | David Rowley | 2022-04-12 21:15:02 +0000 |
| commit | 55ff3563d8fac659147a87ea93ec1464c601107d (patch) | |
| tree | efe16495eef71e08f076857324aced2910f5deaa | |
| parent | 7fc0e7de9fb8306e84d1c15211aba4308f694455 (diff) | |
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/[email protected]
Backpatch-through: 12, where --no-sync was added
| -rw-r--r-- | doc/src/sgml/ref/pg_rewind.sgml | 4 |
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 e808239aa5..69d6924b3a 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> |