8.3 Upgrading to Advanced Server 9.5

Table of Contents Previous Next


8 Upgrading an Installation With pg_upgrade : 8.3 Upgrading to Advanced Server 9.5

The basic steps to perform an upgrade into an empty cluster created with the initdb command are the same as the steps to upgrade into the cluster created by the Advanced Server 9.5 installer, but you can omit Step 2 (Empty the edb database), and substitute the location of the alternate cluster when specifying a target cluster for the upgrade.
If a problem occurs during the upgrade process, you can revert to the previous version. See Section 8.5, Reverting to the Old Cluster for detailed information about this process.
The target cluster must not contain any data; you can create an empty cluster using the initdb command, or you can empty a database that was created during the installation of Advanced Server 9.5. If you have installed Advanced Server in PostgreSQL mode, the installer creates a single database named postgres; if you have installed Advanced Server in Oracle mode, it creates a database named postgres and a database named edb.
The easiest way to empty the target database is to drop the database and then create a new database. Before invoking the DROP DATABASE command, you must disconnect any users or services that are currently using the database.
pgbouncer - The PgBouncer service
ppas-agent-9.5 - The PgAgent service
On Windows, navigate through the 制御 Panel to the Services manager; highlight each service in the Services list, and select Stop.
On Linux, open a terminal window, assume superuser privileges, and navigate to the /etc/init.d directory. Manually stop each service; for example, invoke the command:
To open the EDB-PSQL command line, navigate through the Start menu and select Run SQL Command Line; select EDB-PSQL to open the command line client. When the client opens, connect to the template1 database as the database superuser. If prompted, provide authentication information; then, use the following command to drop the database:
DROP DATABASE database_name;
Where database_name is the name of the database.
CREATE DATABASE database_name;
During the upgrade process, pg_upgrade will connect to the old and new servers several times; to make the connection process easier, you should edit the pg_hba.conf file, setting the authentication mode to trust. To modify the pg_hba.conf file, navigate through the Start menu to each Postgres Plus Advanced Server menu, and open the Expert Configuration menu; select the Edit pg_hba.conf menu option to open the pg_hba.conf file.
You should allow trust authentication for the previous Advanced Server installation, and Advanced Server 9.5 servers. Edit the pg_hba.conf file for both installations of Advanced Server as shown in Figure 8.1.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\575ca32d\trust.png
Figure 8.1 — Configuring Advanced Server to use trust authentication.
If the system is required to maintain md5 authentication mode during the upgrade process, you can specify user passwords for the database superuser in a password file (pgpass.conf on Windows, .pgpass on Linux). For more information about configuring a password file, see the PostgreSQL Core Documentation, available through:
Navigate through the 制御 Panel to the Services manager; highlight each running Advanced Server service displayed in the list, and select Stop.
Open a terminal window, assume superuser privileges, and navigate to the /etc/init.d directory. Manually stop each Advanced Server service at the command line; for example, to stop Advanced Server 9.5 invoke the command:
During the upgrade process, pg_upgrade writes a file to the current working directory of the enterprisedb user; you must invoke pg_upgrade from a directory where the enterprisedb super user has write privileges. After performing the above commands, navigate to a directory in which the enterprisedb user has sufficient privileges to write a file.
pg_upgrade.exe -d "C:\Program Files\PostgresPlus\9.4AS\data"
-D "C:\Program Files\PostgresPlus\9.5AS\data" -U enterprisedb
-b "C:\Program Files\PostgresPlus\9.4AS\bin" -B "C:\Program Files\PostgresPlus\9.5AS\bin" -p 5444 -P 5445 --check
If pg_upgrade alerts you to a missing component, you can use StackBuilder Plus to add the component that contains the component. Before using StackBuilder Plus, you must restart the Advanced Server 9.5 service. After restarting the service, open StackBuilder Plus by navigating through the Start menu to the Postgres Plus Advanced Server 9.5 menu, and selecting StackBuilder Plus. Follow the onscreen advice of the StackBuilder Plus wizard to download and install the missing components.
pg_upgrade.exe -d "C:\Program Files\PostgresPlus\9.4AS\data"
-D "C:\Program Files\PostgresPlus\9.5AS\data" -U enterprisedb
-b "C:\Program Files\PostgresPlus\9.4AS\bin" -B "C:\Program Files\PostgresPlus\9.5AS\bin" -p 5444 -P 5445
\i complete_path_to_script/script.sql
Please Note: If pg_upgrade fails to complete the upgrade process, the old cluster will be unchanged, except that $PGDATA/global/pg_control is renamed to pg_control.old and each tablespace is renamed to tablespace.old. To revert to the pre-invocation state:
Rename $PGDATA/global/pg_control, removing the .old suffix.
If you modified the pg_hba.conf file to permit trust authentication, update the contents of the pg_hba.conf file to reflect your preferred authentication settings.

8 Upgrading an Installation With pg_upgrade : 8.3 Upgrading to Advanced Server 9.5

Table of Contents Previous Next