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

Commitae9acb6

Browse files
committed
Mention that pg_upgrade requires write permission in the current
directory.Per report from Harald Armin Massa.
1 parent6b44b9b commitae9acb6

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

‎doc/src/sgml/pgupgrade.sgml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -272,7 +272,7 @@ NET STOP pgsql-8.3 (<productname>PostgreSQL</> 8.3 and older used a different s
272272
<title>Run <application>pg_upgrade</></title>
273273

274274
<para>
275-
Always run the <application>pg_upgrade</> binaryin the new server, not the old one.
275+
Always run the <application>pg_upgrade</> binaryof the new server, not the old one.
276276
<application>pg_upgrade</> requires the specification of the old and new cluster's
277277
data and executable (<filename>bin</>) directories. You can also specify separate
278278
user and port values, and whether you want the data linked instead of
@@ -306,6 +306,7 @@ pg_upgrade.exe
306306
to perform only the checks, even if the old server is still
307307
running. <command>pg_upgrade --check</> will also outline any
308308
manual adjustments you will need to make after the migration.
309+
<command>pg_upgrade</> requires write permission in the current directory.
309310
</para>
310311

311312
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp