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

Commit5090d70

Browse files
committed
pg_upgrade: improve docs about extension upgrades
The previous wording was unclear about the steps needed to upgradeextensions, and how to update them after pg_upgrade.Reported-by: Dave CramerDiscussion:https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3MMA@mail.gmail.comBackpatch-through: 9.6
1 parent691272c commit5090d70

File tree

1 file changed

+21
-11
lines changed

1 file changed

+21
-11
lines changed

‎doc/src/sgml/ref/pgupgrade.sgml

Lines changed: 21 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -299,17 +299,27 @@ make prefix=/usr/local/pgsql.new install
299299
</step>
300300

301301
<step>
302-
<title>Installcustom shared object files</title>
302+
<title>Installextension shared object files</title>
303303

304304
<para>
305-
Install any custom shared object files (or DLLs) used by the old cluster
306-
into the new cluster, e.g., <filename>pgcrypto.so</filename>,
307-
whether they are from <filename>contrib</filename>
308-
or some other source. Do not install the schema definitions, e.g.,
309-
<command>CREATE EXTENSION pgcrypto</command>, because these will be upgraded
310-
from the old cluster.
311-
Also, any custom full text search files (dictionary, synonym,
312-
thesaurus, stop words) must also be copied to the new cluster.
305+
Many extensions and custom modules, whether from
306+
<filename>contrib</filename> or another source, use shared object
307+
files (or DLLs), e.g., <filename>pgcrypto.so</filename>. If the old
308+
cluster used these, shared object files matching the new server binary
309+
must be installed in the new cluster, usually via operating system
310+
commands. Do not load the schema definitions, e.g., <command>CREATE
311+
EXTENSION pgcrypto</command>, because these will be duplicated from
312+
the old cluster. (Extensions with available updates can be processed
313+
later using <literal>ALTER EXTENSION ... UPDATE</literal>.)
314+
</para>
315+
</step>
316+
317+
<step>
318+
<title>Copy custom full-text search files</title>
319+
320+
<para>
321+
Copy any custom full text search files (dictionary, synonym,
322+
thesaurus, stop words) from the old to the new cluster.
313323
</para>
314324
</step>
315325

@@ -494,10 +504,10 @@ pg_upgrade.exe
494504
</step>
495505

496506
<step>
497-
<title>Installcustom shared object files</title>
507+
<title>Installextension shared object files</title>
498508

499509
<para>
500-
Install the samecustom shared object files on the new standbys
510+
Install the sameextension shared object files on the new standbys
501511
that you installed in the new primary cluster.
502512
</para>
503513
</step>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp