Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 927758f

Browse files
author
Liudmila Mantrova
committed
DOC: sync pgpro-9.6 RNs between PGPRO10 and PGPROEE10 branches to avoid merge conflicts
1 parent 8f36fea commit 927758f

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

doc/src/sgml/release-pro-9.6.sgml

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -120,12 +120,12 @@
120120
<productname>Postgres Pro</productname> 9.6.5.1, it is enough to install the new
121121
version into your current installation directory.
122122
When upgrading from <productname>Postgres Pro</productname> 9.6.4.1 or
123-
lower, you must also use the <literal>pgpro_upgrade</literal> script provided
123+
lower, you must also use the <filename>pgpro_upgrade</filename> script provided
124124
in this distribution. This script updates metadata information to
125125
handle catalog number format change introduced after
126126
<productname>Postgres Pro</productname> 9.6.4.1. If you are upgrading your
127127
<productname>Postgres Pro</productname> installation from a binary package, the
128-
<literal>pgpro_upgrade</literal> script is run automatically, unless you
128+
<filename>pgpro_upgrade</filename> script is run automatically, unless you
129129
are prompted to run it manually.
130130
</para>
131131
<important>
@@ -134,8 +134,7 @@
134134
you must stop postgres service.
135135
The script must be run on behalf of the user owning the database
136136
(typically postgres). Running <literal>pgpro_upgrade</literal>
137-
as root will result in an error. For details, see
138-
<filename>pgpro_upgrade</filename> documentation.
137+
as root will result in an error.
139138
</para>
140139
</important>
141140
<para>If you have compiled <productname>Postgres Pro</productname>

0 commit comments

Comments
 (0)