| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: docs: clarify pg_upgrade's recovery behavior |
| Date: | 2019-04-17 22:01:17 |
| Message-ID: | E1hGscH-0000x2-8N@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
docs: clarify pg_upgrade's recovery behavior
The previous paragraph trying to explain --check, --link, and no --link
modes and the various points of failure was too complex. Instead, use
bullet lists and sublists.
Reported-by: Daniel Gustafsson
Backpatch-through: 9.4
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/64bbe1039962a75cb292fb557e2e79a58c77ec33
Modified Files
--------------
doc/src/sgml/ref/pgupgrade.sgml | 52 ++++++++++++++++++++++++++++-------------
1 file changed, 36 insertions(+), 16 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-04-17 22:12:26 | pgsql: postgresql.conf.sample: add proper defaults for include actions |
| Previous Message | Tom Lane | 2019-04-17 21:57:14 | Re: pgsql: Fix unportable code in pgbench. |