1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00

Update docs for 7.2 mention where appropriate.

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

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