From 5f3f85486584a47fef8f38d442d33eb9791c79b2 Mon Sep 17 00:00:00 2001 From: Pavel Raiskup Date: Wed, 6 Jan 2016 23:56:33 +0100 Subject: 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. --- NEWS | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'NEWS') diff --git a/NEWS b/NEWS index 3a329b6..d056dd6 100644 --- a/NEWS +++ b/NEWS @@ -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. -- cgit