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

Commitc7c801e

Browse files
committed
Improve some wording in pg_upgrade/IMPLEMENTATION
Author: Gurjeet SinghDiscussion:https://postgr.es/m/CABwTF4VFKtKrb78fBnMXwHvOu4a+-7y86siBSEety2knti2eGA@mail.gmail.com
1 parent4800a5d commitc7c801e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎src/bin/pg_upgrade/IMPLEMENTATION

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,9 +48,9 @@ HOW IT WORKS
4848
To use pg_upgrade during an upgrade, start by installing a fresh
4949
cluster using the newest version in a new directory. When you've
5050
finished installation, the new cluster will contain the new executables
51-
and the usual template0, template1, and postgres, but no user-defined
52-
tables. At this point, you can shut down the old and new postmasters and
53-
invoke pg_upgrade.
51+
and the usual template0, template1, and postgres databases, but no
52+
user-definedtables. At this point, you can shut down the old and new
53+
postmasters andinvoke pg_upgrade.
5454

5555
When pg_upgrade starts, it ensures that all required executables are
5656
present and contain the expected version numbers. The verification

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp