If pg_upgrade fails it is OK because we have several other options which we try during hub package upgrade.

To see any errors, run the upgrade with DEBUG=1 defined as an environment variable.

Ticket: ENT-12383
Changelog: title
(cherry picked from commit c3bbbc3)

…ARY_PATH of previous installation"

In the case of 3.21.5 (postgresql 15.6) to 3.25.0a (master, postgresql 17.0) pg_upgrade seems to work fine with the removal of LD_LIBRARY_PATH pointed at the backup.

In other cases we will simply ignore pg_upgrade failures and allow the subsequent migration methods to proceed.
This reverts commit e39924c.

(cherry picked from commit 2c74496)

… if pg_upgrade fails

Ticket: ENT-12383
Changelog: none