File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change 233
233
</listitem>
234
234
<listitem>
235
235
<para>
236
- Handling transactions with serialization or deadlock errors in <application>pg_bench </application>.
236
+ Handling transactions with serialization or deadlock errors in <application>pgbench </application>.
237
237
<!--
238
238
81a4ee1ddffa20f1b738b3c3ccde8611b9b92ee8
239
239
-->
252
252
<para>
253
253
To migrate to <productname>Postgres Pro Enterprise</productname> 10,
254
254
you are recommended to perform a dump/restore using
255
- <xref linkend="app-pg-dumpall">. Using <xref linkend="pgupgrade"> utility
255
+ <xref linkend="app-pg-dumpall">. <xref linkend="pgupgrade"> utility
256
256
can only used when upgrading from <productname>Postgres Pro Enterprise</productname> 9.6 versions.
257
257
</para>
258
258
290
290
291
291
<para>
292
292
When you are using <xref linkend="app-pg-dumpall">
293
- to perform the upgrade, <productname>Postgres Pro</productname> uses
293
+ to perform the upgrade, <productname>Postgres Pro Enterprise </productname> uses
294
294
the collation provider specified with the <command>initdb</command>
295
295
command for the new cluster. In this case, indexes are rebuilt
296
296
automatically. To avoid issues with collation-dependent constraints,
You can’t perform that action at this time.
0 commit comments