summaryrefslogtreecommitdiff
path: root/doc/src/sgml/pgupgrade.sgml
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2015-03-10 22:33:25 -0400
committerPeter Eisentraut <peter_e@gmx.net>2015-04-14 19:26:37 -0400
commit30982be4e5019684e1772dd9170aaa53f5a8e894 (patch)
treeee83c2fa412fb58cfb12c0a74211fb76b8b5eed7 /doc/src/sgml/pgupgrade.sgml
parent936546dcbc24ad1f2b3d33e73aa5c5fde4d2be84 (diff)
downloadpostgresql-30982be4e5019684e1772dd9170aaa53f5a8e894.tar.gz
Integrate pg_upgrade_support module into backend
Previously, these functions were created in a schema "binary_upgrade", which was deleted after pg_upgrade was finished. Because we don't want to keep that schema around permanently, move them to pg_catalog but rename them with a binary_upgrade_... prefix. The provided functions are only small wrappers around global variables that were added specifically for pg_upgrade use, so keeping the module separate does not create any modularity. The functions still check that they are only called in binary upgrade mode, so it is not possible to call these during normal operation. Reviewed-by: Michael Paquier <michael.paquier@gmail.com>
Diffstat (limited to 'doc/src/sgml/pgupgrade.sgml')
-rw-r--r--doc/src/sgml/pgupgrade.sgml5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 0d79fb5f52..45bceff9be 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -253,11 +253,10 @@ make prefix=/usr/local/pgsql.new install
</step>
<step>
- <title>Install pg_upgrade and pg_upgrade_support</title>
+ <title>Install pg_upgrade</title>
<para>
- Install the <application>pg_upgrade</> binary and
- <application>pg_upgrade_support</> library in the new PostgreSQL
+ Install the <application>pg_upgrade</> binary in the new PostgreSQL
installation.
</para>
</step>