diff options
| author | Bruce Momjian <bruce@momjian.us> | 2021-08-03 11:27:33 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2021-08-03 11:27:33 -0400 |
| commit | 5090d709f172ecd00b16b6e336c8c149a3f3d33d (patch) | |
| tree | 9cc28d2816b09a1ae1ee2735aa3836d869456976 | |
| parent | 691272cae96b3c947d3d2d4d8c43c499e72c65a2 (diff) | |
| download | postgresql-5090d709f172ecd00b16b6e336c8c149a3f3d33d.tar.gz postgresql-5090d709f172ecd00b16b6e336c8c149a3f3d33d.zip | |
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
| -rw-r--r-- | doc/src/sgml/ref/pgupgrade.sgml | 32 |
1 files changed, 21 insertions, 11 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index a83c63cd98f..0a714658050 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -299,17 +299,27 @@ make prefix=/usr/local/pgsql.new install </step> <step> - <title>Install custom shared object files</title> + <title>Install extension shared object files</title> <para> - Install any custom shared object files (or DLLs) used by the old cluster - into the new cluster, e.g., <filename>pgcrypto.so</filename>, - whether they are from <filename>contrib</filename> - or some other source. Do not install the schema definitions, e.g., - <command>CREATE EXTENSION pgcrypto</command>, because these will be upgraded - from the old cluster. - Also, any custom full text search files (dictionary, synonym, - thesaurus, stop words) must also be copied to the new cluster. + Many extensions and custom modules, whether from + <filename>contrib</filename> or another source, use shared object + files (or DLLs), e.g., <filename>pgcrypto.so</filename>. If the old + cluster used these, shared object files matching the new server binary + must be installed in the new cluster, usually via operating system + commands. Do not load the schema definitions, e.g., <command>CREATE + EXTENSION pgcrypto</command>, because these will be duplicated from + the old cluster. (Extensions with available updates can be processed + later using <literal>ALTER EXTENSION ... UPDATE</literal>.) + </para> + </step> + + <step> + <title>Copy custom full-text search files</title> + + <para> + Copy any custom full text search files (dictionary, synonym, + thesaurus, stop words) from the old to the new cluster. </para> </step> @@ -494,10 +504,10 @@ pg_upgrade.exe </step> <step> - <title>Install custom shared object files</title> + <title>Install extension shared object files</title> <para> - Install the same custom shared object files on the new standbys + Install the same extension shared object files on the new standbys that you installed in the new primary cluster. </para> </step> |