]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3ef5e16) | patch
docs: clarify pg_upgrade's recovery behavior
authorBruce Momjian <bruce@momjian.us>
Wed, 17 Apr 2019 22:01:01 +0000 (18:01 -0400)
committerBruce Momjian <bruce@momjian.us>
Wed, 17 Apr 2019 22:01:01 +0000 (18:01 -0400)
commit39a93fd294a0442292de70f2e42e9b1da1c4e3b6
tree91e07b584545fcef5de917ec57c4086c4e374fd6tree | snapshot
parent3ef5e16c618177160bc5f95216dccab3588defdccommit | diff
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
doc/src/sgml/pgupgrade.sgml diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.