| From: | David Rowley <drowley(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Docs: avoid confusing use of the word "synchronized" |
| Date: | 2022-04-12 21:17:00 |
| Message-ID: | E1neNsi-000ESB-5V@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/3a95dfe4025f48fb57262ce590ba397a80a1a7b6
Modified Files
--------------
doc/src/sgml/ref/pg_rewind.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2022-04-12 21:17:45 | pgsql: Docs: avoid confusing use of the word "synchronized" |
| Previous Message | David Rowley | 2022-04-12 21:16:19 | pgsql: Docs: avoid confusing use of the word "synchronized" |