Fix version numbering foulups exposed by 10.1.
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 7 Nov 2017 00:46:52 +0000 (19:46 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 7 Nov 2017 00:46:52 +0000 (19:46 -0500)
commitd0c80c17f1a6d0b93d2ca14fe47d83b131ce9108
tree588da68978586a05294d294513aabeea79d58407
parent92d830f4bff643953a09563abaa106af42625207
Fix version numbering foulups exposed by 10.1.

configure computed PG_VERSION_NUM incorrectly.  (Coulda sworn I tested
that logic back when, but it had an obvious thinko.)

pg_upgrade had not been taught about the new dispensation with just
one part in the major version number.

Both things accidentally failed to fail with 10.0, but with 10.1 we
got the wrong results.

Per buildfarm.
configure
configure.in
src/bin/pg_upgrade/exec.c
src/bin/pg_upgrade/server.c