diff options
author | Peter Eisentraut <peter@eisentraut.org> | 2019-07-27 07:56:20 +0200 |
---|---|---|
committer | Peter Eisentraut <peter@eisentraut.org> | 2019-07-27 08:19:04 +0200 |
commit | 959f6d6a1821b7d9068244f500dd80953e768d16 (patch) | |
tree | b42411a991355cbc24f3813f0ea8accdd18f16ea /src/backend/utils/adt/arrayfuncs.c | |
parent | 0befb4f31386efb622e4df9f3a313aa1f2e17899 (diff) | |
download | postgresql-959f6d6a1821b7d9068244f500dd80953e768d16.tar.gz postgresql-959f6d6a1821b7d9068244f500dd80953e768d16.zip |
pg_upgrade: Default new bindir to pg_upgrade location
Make the directory where the pg_upgrade binary resides the default for
new bindir, as running the pg_upgrade binary from where the new
cluster is installed is a very common scenario. Setting this as the
defauly bindir for the new cluster will remove the need to provide it
explicitly via -B in many cases.
To support directories being missing from option parsing, extend the
directory check with a missingOk mode where the path must be filled at
a later point before being used. Also move the exec_path check to
earlier in setup to make sure we know the new cluster bindir when we
scan for required executables.
This removes the exec_path from the OSInfo struct as it is not used
anywhere.
Author: Daniel Gustafsson <daniel@yesql.se>
Reviewed-by: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Discussion: https://www.postgresql.org/message-id/flat/9328.1552952117@sss.pgh.pa.us
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions