diff options
| author | Pavel Raiskup <praiskup@redhat.com> | 2016-01-06 23:56:33 +0100 |
|---|---|---|
| committer | Pavel Raiskup <praiskup@redhat.com> | 2016-01-07 00:05:44 +0100 |
| commit | 5f3f85486584a47fef8f38d442d33eb9791c79b2 (patch) | |
| tree | 6ed703fb47eaa79079d1b25c250bb3a74aa15df9 /NEWS | |
| parent | 47fe731d3ed9b4a0fd60ffc4e79c294251763b1a (diff) | |
| download | postgresql-setup-5f3f85486584a47fef8f38d442d33eb9791c79b2.tar.gz postgresql-setup-5f3f85486584a47fef8f38d442d33eb9791c79b2.tar.xz postgresql-setup-5f3f85486584a47fef8f38d442d33eb9791c79b2.zip | |
postgresql-setup: reflect pg_upgrade movement
The pg_upgrade binary is not in postgresql-upgrade package now.
In some upgrade scenarios, postgresql-upgrade is redundant package
(SCLs/PGRPMSs). Hack the code so postgresql-setup is able to
correctly advice which package should be installed to make the
"old" engine available.
* postgresql-setup.in (upgrade): Don't check for pg_upgrade binary
existence but rather for postgres binary, and warn user with
proper package name if missing.
* share/postgresql-setup/library.sh.in (parse_upgrade_setup):
White-list also 'package' constant name.
* configure.ac: Bump version.
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -1,5 +1,12 @@ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +New in 4.0 version: + +* The postgresql-upgrade package is now optional packaging feature, for the + postgresql-setup --upgrade scenario it might/might not be needed. + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + Bugfixes in 3.5 version * Fix spelling in error message regarding data-dir mountpoint. |