pgsql: docs: clarify pg_upgrade's recovery behavior

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-0000xA-99@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

Discussion: https://postgr.es/m/qtqiv7hI87s_Xvz5ZXHCaH-1-_AZGpIDJowzlRjF3-AbCr3RhSNydM_JCuJ8DE4WZozrtxhIWmyYTbv0syKyfGB6cYMQitp9yN-NZMm-oAo=@yesql.se

Backpatch-through: 9.4

Branch
------
REL9_5_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/dfdab98cdee892ac4a557161a9aaef5715901175

Modified Files
--------------
doc/src/sgml/ref/pgupgrade.sgml | 52 ++++++++++++++++++++++++++++-------------
1 file changed, 36 insertions(+), 16 deletions(-)

Browse pgsql-committers by date

  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.