--Apple-Mail=_ED6F23F2-EAD4-4794-9104-AE8484B6590A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I'm on a RHEL 7, trying to install a ovirt 3.6.0.3. The database used is on a remote server, using a postgres 9.4. The backup of the previous database fails with : 2015-12-10 12:04:13 DEBUG = otopi.**FILTERED**_engine_setup.engine_common.database = database.backup:661 db backup res {'result': [{'stderr': 'pg_dump: = server version: 9.4.5; pg_dump version: 9.2.14\npg_dump: aborting = because of server version mismatch\n', 'rc': 1}], 'stdout': ''} But the good pg_dump is in the path: ~# type pg_dump pg_dump is /usr/pgsql-9.4/bin/pg_dump Although in the log file: 2015-12-10 12:40:19 DEBUG otopi.context context.dumpEnvironment:510 ENV = COMMAND/pg_dump=3Dstr:'/bin/pg_dump' Why ? How can I enforce the use of the latest pg_dump without rewrinting = the '/bin/pg_dump' which is owned by the official postgres package ? --Apple-Mail=_ED6F23F2-EAD4-4794-9104-AE8484B6590A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D"">I'm on a RHEL 7, trying to install a ovirt 3.6.0.3.<div = class=3D""><br class=3D""></div><div class=3D"">The database used is on = a remote server, using a postgres 9.4.</div><div class=3D""><br = class=3D""></div><div class=3D"">The backup of the previous database = fails with :</div><div class=3D""><div style=3D"margin: 0px; font-size: = 11px; font-family: Menlo;" class=3D"">2015-12-10 12:04:13 DEBUG = otopi.**FILTERED**_engine_setup.engine_common.database = database.backup:661 db backup res {'result': [{'stderr': 'pg_dump: = server version: 9.4.5; pg_dump version: 9.2.14\npg_dump: aborting = because of server version mismatch\n', 'rc': 1}], 'stdout': = ''}</div></div><div class=3D""><br class=3D""></div><div class=3D"">But = the good pg_dump is in the path:</div><div class=3D""><br = class=3D""></div><div class=3D""><div style=3D"margin: 0px; font-size: = 11px; font-family: Menlo;" class=3D"">~# type pg_dump</div><div = style=3D"margin: 0px; font-size: 11px; font-family: Menlo;" = class=3D"">pg_dump is /usr/pgsql-9.4/bin/pg_dump</div></div><div = class=3D""><br class=3D""></div><div class=3D"">Although in the log = file:</div><div class=3D""><br class=3D""></div><div class=3D""><div = style=3D"margin: 0px; font-size: 11px; font-family: Menlo;" = class=3D"">2015-12-10 12:40:19 DEBUG otopi.context = context.dumpEnvironment:510 ENV COMMAND/<span = style=3D"font-variant-ligatures: no-common-ligatures; color: #ffffff; = background-color: #000000" class=3D"">pg_dump</span>=3Dstr:'/bin/<span = style=3D"font-variant-ligatures: no-common-ligatures; color: #ffffff; = background-color: #000000" class=3D"">pg_dump</span>'</div></div><div = class=3D""><br class=3D""></div><div class=3D"">Why ? How can I enforce = the use of the latest pg_dump without rewrinting the <span = style=3D"font-family: Menlo; font-size: 11px;" = class=3D"">'/bin/</span><span style=3D"font-family: Menlo; font-size: = 11px; color: rgb(255, 255, 255); background-color: rgb(0, 0, 0);" = class=3D"">pg_dump</span><span style=3D"font-family: Menlo; font-size: = 11px;" class=3D"">'</span> which is owned by the official postgres = package ?</div><div class=3D""><br class=3D""></div></body></html>= --Apple-Mail=_ED6F23F2-EAD4-4794-9104-AE8484B6590A--