summaryrefslogtreecommitdiff
path: root/configure
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-11-06 19:46:52 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-11-06 19:46:52 -0500
commit958fe549884928cd3bdf009993e9a05df5fd6cee (patch)
treee86b711e478c89d79bba410e27fd062e837d8761 /configure
parent0b35d54c6fc4d98f8e8b38770b53c7358ebf4444 (diff)
downloadpostgresql-958fe549884928cd3bdf009993e9a05df5fd6cee.tar.gz
Fix version numbering foulups exposed by 10.1.REL_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.
Diffstat (limited to 'configure')
-rwxr-xr-xconfigure2
1 files changed, 1 insertions, 1 deletions
diff --git a/configure b/configure
index 353cbe00ca..d9298bf531 100755
--- a/configure
+++ b/configure
@@ -16749,7 +16749,7 @@ _ACEOF
# awk -F is a regex on some platforms, and not on others, so make "." a tab
PG_VERSION_NUM="`echo "$PACKAGE_VERSION" | sed 's/[A-Za-z].*$//' |
tr '.' ' ' |
-$AWK '{printf "%d%02d%02d", $1, $2, (NF >= 3) ? $3 : 0}'`"
+$AWK '{printf "%d%04d", $1, $2}'`"
cat >>confdefs.h <<_ACEOF
#define PG_VERSION_NUM $PG_VERSION_NUM