8.2 Invoking pg_upgrade

Table of Contents Previous Next



When invoking pg_upgrade, you must specify the location of the old and new cluster's PGDATA and executable (/bin) directories, as well as the name of the Advanced Server superuser, and the ports on which the installations are listening. A typical call to invoke pg_upgrade to migrate from Advanced Server 9.3 to Advanced Server 9.4 takes the form:
pg_upgrade --old-datadir path_to_9.3_data_directory --new-datadir path_to_9.4_data_directory --user superuser_name --old-bindir path_to_9.3_bin_directory --new-bindir path_to_9.4_bin_directory --old-port 9.3_port --new-port 9.4_port
--old-datadir path_to_9.3_data_directory
Use the --old-datadir option to specify the complete path to the data directory within the Advanced Server 9.3 installation.
--new-datadir path_to_9.4_data_directory
Use the --new-datadir option to specify the complete path to the data directory within the Advanced Server 9.4 installation.
--username superuser_name
Include the --username option to specify the name of the Advanced Server superuser. The superuser name should be the same in both versions of Advanced Server. By default, when Advanced Server is installed in Oracle mode, the superuser is named enterprisedb. If installed in PostgreSQL mode, the superuser is named postgres.
--old-bindir path_to_9.3_bin_directory
Use the --old-bindir option to specify the complete path to the bin directory in the Advanced Server 9.3 installation.
--new-bindir path_to_9.4_bin_directory
Use the --new-bindir option to specify the complete path to the bin directory in the Advanced Server 9.4 installation.
--old-port 9.3_port
Include the --old-port option to specify the port on which Advanced Server 9.3 listens for connections.
--new-port 9.4_port
Include the --new-port option to specify the port on which Advanced Server 9.4 listens for connections.


Table of Contents Previous Next