|
54 | 54 | workers. (See <xref linkend="pg-wait-sampling">.)</para> |
55 | 55 | </listitem> |
56 | 56 | <listitem><para>Added support for timestamp output in |
57 | | - the <application>pg_xlogdump</application>extension.</para></listitem> |
| 57 | + the <application>pg_xlogdump</application>application.</para></listitem> |
58 | 58 | <listitem> |
59 | 59 | <para>Added support for one-time background jobs in |
60 | 60 | <application>pgpro_scheduler</application>. You can now submit jobs |
|
119 | 119 | <para>If you use binary packages, and your database is in the default |
120 | 120 | location, this upgrade should be performed automatically. If you've |
121 | 121 | compiled <productname>Postgres Pro Enterprise</productname> from source or created your database in |
122 | | - a non-default location running <literal>initdb</literal> manually, you |
| 122 | + a non-default location, running <literal>initdb</literal> manually, you |
123 | 123 | should run the <literal>pgpro_upgrade</literal> script provided in this |
124 | 124 | distribution. |
125 | 125 | </para> |
|
166 | 166 | use of <xref linkend="pgupgrade">, is required for those |
167 | 167 | wishing to migrate data from any previous major release.</para> |
168 | 168 |
|
169 | | - <para>Dump/restore is neccessary when migrating from PostgreSQL |
170 | | - or Postgres Pro Standard edition.</para> |
| 169 | + <para>Dump/restore is neccessary when migrating from<productname>PostgreSQL</productname> |
| 170 | + or<productname>Postgres Pro Standard</productname> edition.</para> |
171 | 171 |
|
172 | | - <para>When upgrading from previous releases of Postgres Pro or from |
173 | | -vanillaPostgreSQL 9.6.x, some catalog changes should be applied.</para> |
| 172 | + <para>For upgrades from previous releases of<productname>Postgres Pro Standard</productname> or from |
| 173 | +<productname>PostgreSQL</productname> 9.6.x, some catalog changes should be applied.</para> |
174 | 174 |
|
175 | 175 | <para>If you use binary packages, and your database is in the default |
176 | 176 | location, this upgrade should be performed automatically. If you've |
177 | | - compiled Postgres Pro from source or create your database in |
| 177 | + compiled<productname>Postgres Pro</productname> from source or create your database in |
178 | 178 | non-default location, running <literal>initdb</literal> manually, you |
179 | 179 | should run <literal>pgpro_upgrade</literal> script provided in this |
180 | 180 | distribution. |
|