From f0fc95612d741bffc926b9641873dc8c32e4bc69 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 26 Jan 2007 22:52:50 +0000 Subject: [PATCH] Update wording of installation when upgrading, to more clearly distinguish major vs minor release upgrades. --- doc/src/sgml/installation.sgml | 96 +++++++++++++++++++++------------- 1 file changed, 61 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml index 92a7d7b48fb..719e9c1fca7 100644 --- a/doc/src/sgml/installation.sgml +++ b/doc/src/sgml/installation.sgml @@ -1,4 +1,4 @@ - + <![%standalone-include[<productname>PostgreSQL</>]]> @@ -367,36 +367,39 @@ su - postgres ]]> <sect1 id="install-upgrading"> - <title>If You Are Upgrading + Upgrading upgrading - The internal data storage format changes with new releases of - PostgreSQL. Therefore, if you are upgrading an - existing installation that does not have a version number + These instructions assume that your existing installation is under the + /usr/local/pgsql directory, and that the data area is in + /usr/local/pgsql/data. Substitute your paths + appropriately. + + + + The internal data storage format typically changes in every major + release of PostgreSQL. Therefore, if you are upgrading + an existing installation that does not have a version number of &majorversion;.x, you must back up and restore your - data as shown here. These instructions assume that your existing - installation is under the /usr/local/pgsql directory, - and that the data area is in /usr/local/pgsql/data. - Substitute your paths appropriately. + data. If you are upgrading from the same major version, the new version + can use your current data files, so a backup and restore is optional. + If you wish to avoid the backup/restore, merely skip those steps below. - Make sure that your database is not updated during or after the - backup. This does not affect the integrity of the backup, but the - changed data would of course not be included. If necessary, edit - the permissions in the file - /usr/local/pgsql/data/pg_hba.conf (or equivalent) to - disallow access from everyone except you. + If making a backup, make sure that your database is being updated. + This does not affect the integrity of the backup, but the changed + data would of course not be included. If necessary, edit the + permissions in the file /usr/local/pgsql/data/pg_hba.conf + (or equivalent) to disallow access from everyone except you. - - pg_dumpall @@ -429,9 +432,7 @@ su - postgres - If you are installing the new version at the same location as the - old one then shut down the old server, at the latest before you - install the new files: + Shut down the old server: pg_ctl stop @@ -448,38 +449,63 @@ su - postgres - If you are installing in the same place as the old version then - it is also a good idea to move the old installation out of the - way, in case you have trouble and need to revert to it. - Use a command like this: - + If restoring from backup, rename or delete the old installation + directory. It is a good idea to rename the directory, rather than + delete it, in case you have trouble and need to revert to it. Keep + in mind the directory might consume significant disk space. To rename + the directory, use a command like this: + mv /usr/local/pgsql /usr/local/pgsql.old - - - After you have installed PostgreSQL &version;, create a new database - directory and start the new server. Remember that you must execute - these commands while logged in to the special database user account - (which you already have if you are upgrading). + + + Install the new version of PostgreSQL as + outlined in + .]]> + + + + + + Create a new database cluster if needed. Remember that you must + execute these commands while logged in to the special database user + account (which you already have if you are upgrading). /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data + + + + + + + Start the database server, again from the special database user + account: + /usr/local/pgsql/bin/postgres -D /usr/local/pgsql/data - Finally, restore your data with + + + + + + Finally, restore your data from backup with /usr/local/pgsql/bin/psql -d postgres -f outputfile - using the new psql. - + using the new psql. + + + Further discussion appears in ,]]> - which you are encouraged to read in any case. + including instructions on how the previous installation can continue + running while the new installation is installed. -- 2.39.5