|
63 | 63 | <para>To upgrade from a <productname>Postgres Pro</productname> version based on |
64 | 64 | any previous <productname>PostgreSQL</productname> major release, you can perform a dump/restore using |
65 | 65 | <xref linkend="app-pg-dumpall">, or use the <xref linkend="pgupgrade"> utility. |
66 | | - The first option is safer, while the second is faster and can |
| 66 | + The first option is safer, while the second is faster and can significantly |
67 | 67 | speed up the upgrade process for large databases. |
68 | 68 | </para> |
69 | 69 | <para>To upgrade from a <productname>Postgres Pro</productname> version |
70 | 70 | based on the same <productname>PostgreSQL</productname> major release, |
71 | | - the <literal>pgpro_upgrade</literal> script provided |
72 | | -in this distribution is required: |
73 | | -<itemizedlist> |
74 | | - <listitem> |
75 | | - <para>If you are upgrading your <productname>Postgres Pro</productname> |
76 | | -installation from a binary package, the <literal>pgpro_upgrade</literal> script |
77 | | -is run automatically, or you are prompted to run it manually. |
78 | | - </para> |
79 | | - </listitem> |
80 | | - <listitem> |
81 | | - <para>If youhave compiled <productname>Postgres Pro</productname> |
82 | | - from source code or created your database in a non-default location, |
83 | | - you must always run the<literal>pgpro_upgrade</literal> script manually. |
84 | | - Before running the script, youshouldstop postgres service. |
85 | | - Script should be run on behalf of the user owning the database |
86 | | - (typically postgres) and PGDATA environment variable should be |
87 | | - set to the directory where database resides. |
88 | | - </para> |
89 | | - </listitem> |
90 | | - </itemizedlist> |
| 71 | +a dump/restore is not required. Instead ofthe <literal>pg_upgrade</literal>, |
| 72 | +you must use the <literal>pgpro_upgrade</literal> script provided |
| 73 | +in this distribution. This script updates metadata information to |
| 74 | +handle catalog number format change introduced in |
| 75 | +<productname>Postgres Pro</productname> 9.6.4.1.If you are upgrading your |
| 76 | +<productname>Postgres Pro</productname>installation from a binary package, the |
| 77 | +<literal>pgpro_upgrade</literal> scriptis run automatically, or you |
| 78 | +are prompted to run it manually. |
| 79 | +<important> |
| 80 | + <para> |
| 81 | + If yourun <literal>pgpro_upgrade</literal> manually, |
| 82 | +you must stop postgres service. |
| 83 | +The script must be run on behalf of theuser owning the database |
| 84 | +(typically postgres) and PGDATA environment variableshouldbe |
| 85 | +set to the directory where database resides. Running <literal>pgpro_upgrade</literal> |
| 86 | +as root will result in an error. |
| 87 | +If you have compiled <productname>Postgres Pro</productname> |
| 88 | +from source code or created your database in a non-default location, |
| 89 | +you must run the <literal>pgpro_upgrade</literal> script manually. |
| 90 | + </para> |
91 | 91 | <note> |
92 | 92 | <para>On RPM-based Linux distributions, if you are upgrading from |
93 | 93 | version 9.6.2.1 or lower, make sure to move the data directory from |
94 | 94 | <filename>pgsql</filename> to the <filename>pgpro</filename> |
95 | 95 | directory before running the <literal>pgpro_upgrade</literal> script. |
96 | | - Besides, after you upgrade to a newer version, you will have to use |
97 | | - the <literal>systemd</literal> service manager. |
98 | 96 | </para> |
99 | 97 | </note> |
100 | 98 | </para> |
|
