Improve wording of some pg_upgrade failure reports.
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 29 Apr 2021 19:40:34 +0000 (15:40 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 29 Apr 2021 19:40:34 +0000 (15:40 -0400)
commitc9c37ae03fea0c8ad467392ddf03940b61974935
tree04426a57491d3c4bc4c3226fb48d481c2da14bb5
parent57c081de0afcd01bf47c46f015bf8886b01c2c21
Improve wording of some pg_upgrade failure reports.

Don't advocate dropping a whole table when dropping a column would
serve.  While at it, try to make the layout of these messages a
bit cleaner and more consistent.

Per suggestion from Daniel Gustafsson.  No back-patch, as we generally
don't like to churn translatable messages in released branches.

Discussion: https://postgr.es/m/2798740.1619622555@sss.pgh.pa.us
src/bin/pg_upgrade/check.c
src/bin/pg_upgrade/version.c