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

Commitc120dd2

Browse files
committed
Update wording for minor release upgrades, per Alvaro.
1 parent631d701 commitc120dd2

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

‎doc/src/sgml/installation.sgml

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.277 2007/01/27 01:27:36 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.278 2007/01/29 21:49:17 momjian Exp $ -->
22

33
<chapter id="installation">
44
<title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -385,9 +385,10 @@ su - postgres
385385
release of <productname>PostgreSQL</>. Therefore, if you are upgrading
386386
an existing installation that does not have a version number of
387387
<quote>&majorversion;.x</quote>, you must back up and restore your
388-
data. If you are upgrading from the same major version, the new version
389-
can use your current data files so you should skip the backup and
390-
restore steps below because they are unnecessary.
388+
data. If you are upgrading from <productname>PostgreSQL</>
389+
<quote>&majorversion;.x</quote>, the new version can use your current
390+
data files so you should skip the backup and restore steps below because
391+
they are unnecessary.
391392
</para>
392393

393394
<procedure>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp