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