Skip to content

Commit ead4ae0

Browse files
committed
pg_upgrade: improve docs about extension upgrades
The previous wording was unclear about the steps needed to upgrade extensions, and how to update them after pg_upgrade. Reported-by: Dave Cramer Discussion: https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3MMA@mail.gmail.com Backpatch-through: 9.6
1 parent 22023dd commit ead4ae0

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
@@ -298,17 +298,27 @@ make prefix=/usr/local/pgsql.new install
298298
</step>
299299

300300
<step>
301-
<title>Install custom shared object files</title>
301+
<title>Install extension shared object files</title>
302302

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

@@ -493,10 +503,10 @@ pg_upgrade.exe
493503
</step>
494504

495505
<step>
496-
<title>Install custom shared object files</title>
506+
<title>Install extension shared object files</title>
497507

498508
<para>
499-
Install the same custom shared object files on the new standbys
509+
Install the same extension shared object files on the new standbys
500510
that you installed in the new primary cluster.
501511
</para>
502512
</step>

0 commit comments

Comments
 (0)