| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix version numbering foulups exposed by 10.1. |
| Date: | 2017-11-07 00:47:04 |
| Message-ID: | E1eBs2i-0005AQ-Pm@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/d0c80c17f1a6d0b93d2ca14fe47d83b131ce9108
Modified Files
--------------
configure | 2 +-
configure.in | 2 +-
src/bin/pg_upgrade/exec.c | 23 ++++++++++++++---------
src/bin/pg_upgrade/server.c | 18 +++++++++++++-----
4 files changed, 29 insertions(+), 16 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2017-11-07 17:32:27 | pgsql: Exclude pg_internal.init from BASE_BACKUP |
| Previous Message | Vik Fearing | 2017-11-07 00:10:26 | Re: pgsql: Stamp 9.2.24. |