database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-12 21:01:52 +03:00
Code Activity

Docs: avoid confusing use of the word "synchronized"

Browse Source 
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
This commit is contained in:
David Rowley
2022-04-13 09:17:56 +12:00
parent 989d3e4a29
commit af3e3a9b4f
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/ref/pg_rewind.sgml
View File

@ -182,8 +182,8 @@ PostgreSQL documentation
to be written safely to disk. This option causes to be written safely to disk. This option causes
<command>pg_rewind</command> to return without waiting, which is <command>pg_rewind</command> to return without waiting, which is
faster, but means that a subsequent operating system crash can leave faster, but means that a subsequent operating system crash can leave
the synchronized data directory corrupt. Generally, this option is the data directory corrupt. Generally, this option is useful for
useful for testing but should not be used when creating a production testing but should not be used when creating a production
installation. installation.
</para> </para>
</listitem> </listitem>