mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-11-27 07:21:09 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update docs for 7.2 mention where appropriate.

Browse Source
This commit is contained in:
Bruce Momjian 2001-10-01 17:46:46 +00:00
parent 87fd2dbe7c
commit 735594ff08
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
INSTALL
View File

@ -76,7 +76,7 @@ If You Are 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 "7.1.x", you must back up and restore your data as shown
a version number "7.2.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.
@ -97,7 +97,7 @@ here. These instructions assume that your existing installation is under the
do this.
Make sure that you use the pg_dumpall command from the version you are
currently running. 7.1's pg_dumpall should not be used on older
currently running. 7.2's pg_dumpall should not be used on older
databases.
3. If you are installing the new version at the same location as the old
@ -125,7 +125,7 @@ here. These instructions assume that your existing installation is under the
mv /usr/local/pgsql /usr/local/pgsql.old
After you have installed PostgreSQL 7.1, create a new database directory and
After you have installed PostgreSQL 7.2, 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).
@ -736,7 +736,7 @@ tests pass.
Unsupported Platforms. The following platforms have not been verified to
work. Platforms listed for version 6.3.x and later should also work with
7.1, but we did not receive explicit confirmation of such at the time this
7.2, but we did not receive explicit confirmation of such at the time this
list was compiled. We include these here to let you know that these
platforms could be supported if given some attention.

10
doc/src/sgml/backup.sgml
View File

@ -1,4 +1,4 @@
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.15 2001/09/10 07:17:01 ishii Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.16 2001/10/01 17:46:46 momjian Exp $ -->
<chapter id="backup">
<title>Backup and Restore</title>
@ -234,7 +234,7 @@ cat <replaceable class="parameter">filename</replaceable>* | psql <replaceable c
</formalpara>
<formalpara>
<title>Use the custom dump format (V7.1).</title>
<title>Use the custom dump format.</title>
<para>
If PostgreSQL was built on a system with the <application>zlib</> compression library
installed, the custom dump format will compress data as it writes it
@ -368,8 +368,8 @@ tar -cf backup.tar /usr/local/pgsql/data
As a general rule, the internal data storage format is subject to
change between releases of <productname>Postgres</>. This does not
apply to different <quote>patch levels</quote>, these always have
compatible storage formats. For example, releases 6.5.3, 7.0.1, and
7.1 are not compatible, whereas 7.0.2 and 7.0.1 are. When you
compatible storage formats. For example, releases 7.0.1, 7.1.2, and
7.2 are not compatible, whereas 7.1.2 and 7.1.1 are. When you
update between compatible versions, then you can simply reuse the
data area in disk by the new executables. Otherwise you need to
<quote>back up</> your data and <quote>restore</> it on the new
@ -409,7 +409,7 @@ pg_dumpall -p 5432 | psql -d template1 -p 6543
pg_dumpall > backup
pg_ctl stop
mv /usr/local/pgsql /usr/local/pgsql.old
cd /usr/src/postgresql-7.1
cd /usr/src/postgresql-7.2
gmake install
initdb -D /usr/local/pgsql/data
postmaster -D /usr/local/pgsql/data