Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit27552ce

Browse files
committed
Update installation wording for an upgrade to state that dump/restore
should not be done, per Peter.
1 parentadef25e commit27552ce

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎doc/src/sgml/installation.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.276 2007/01/26 22:52:50 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.277 2007/01/27 01:27:36 momjian Exp $ -->
22

33
<chapter id="installation">
44
<title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -386,8 +386,8 @@ su - postgres
386386
an existing installation that does not have a version number of
387387
<quote>&majorversion;.x</quote>, you must back up and restore your
388388
data. If you are upgrading from the same major version, the new version
389-
can use your current data files, soa backup and restore is optional.
390-
If you wish to avoid the backup/restore, merely skip those steps below.
389+
can use your current data files soyou should skip the backup and
390+
restore steps below because they are unnecessary.
391391
</para>
392392

393393
<procedure>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp