|
76 | 76 | <productname>Postgres Pro</productname> installation from a binary package, the |
77 | 77 | <literal>pgpro_upgrade</literal> script is run automatically, or you |
78 | 78 | are prompted to run it manually. |
| 79 | + </para> |
79 | 80 | <important> |
80 | 81 | <para> |
81 | 82 | If you run <literal>pgpro_upgrade</literal> manually, |
|
84 | 85 | (typically postgres) and PGDATA environment variable should be |
85 | 86 | set to the directory where database resides. Running <literal>pgpro_upgrade</literal> |
86 | 87 | as root will result in an error. |
87 | | - </para> |
| 88 | +</para> |
88 | 89 | </important> |
89 | | - If you have compiled <productname>Postgres Pro</productname> |
| 90 | +<para>If you have compiled <productname>Postgres Pro</productname> |
90 | 91 | from source code or created your database in a non-default location, |
91 | 92 | you must run the <literal>pgpro_upgrade</literal> script manually. |
92 | 93 | </para> |
|
97 | 98 | directory before running the <literal>pgpro_upgrade</literal> script. |
98 | 99 | </para> |
99 | 100 | </note> |
100 | | - </para> |
101 | 101 | <para>To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore using |
102 | 102 | <xref linkend="app-pg-dumpall">. |
103 | 103 | </para> |
|
