mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-06 15:24:56 +08:00
Fix bogus logic for checking executables' versions within pg_upgrade.
Somebody messed up a refactoring here. As it stood, we'd check pg_ctl's --version output twice for each cluster. Worse, the first check for the new cluster's version happened before we'd done any validate_exec checks there, breaking the check ordering the code intended. A. Akenteva Discussion: https://postgr.es/m/f9266a85d918a3cf3a386b5148aee666@postgrespro.ru
This commit is contained in:
parent
20d9adab60
commit
9be95ef156
@ -382,12 +382,11 @@ check_bin_dir(ClusterInfo *cluster)
|
||||
validate_exec(cluster->bindir, "pg_ctl");
|
||||
|
||||
/*
|
||||
* Fetch the binary versions after checking for the existence of pg_ctl,
|
||||
* this gives a correct error if the binary used itself for the version
|
||||
* fetching is broken.
|
||||
* Fetch the binary version after checking for the existence of pg_ctl.
|
||||
* This way we report a useful error if the pg_ctl binary used for version
|
||||
* fetching is missing/broken.
|
||||
*/
|
||||
get_bin_version(&old_cluster);
|
||||
get_bin_version(&new_cluster);
|
||||
get_bin_version(cluster);
|
||||
|
||||
/* pg_resetxlog has been renamed to pg_resetwal in version 10 */
|
||||
if (GET_MAJOR_VERSION(cluster->bin_version) < 1000)
|
||||
|
Loading…
Reference in New Issue
Block a user