Skip to content

Commit a334f33

Browse files
committed
Update release notes
1 parent f37f286 commit a334f33

File tree

1 file changed

+27
-4
lines changed

1 file changed

+27
-4
lines changed

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

Lines changed: 27 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,14 @@
44
<title>Postgres Pro 9.6.0.1</title>
55
<note>
66
<title>Release Date</title>
7-
<simpara>2016-10-XX</simpara>
7+
<simpara>2016-10-07</simpara>
88
</note>
99
<sect2>
1010
<title>Overview</title>
1111
<para>This release is based on <productname>PostgreSQL</productname>
1212
9.6.0</para>
13-
<para>Major enhancements over <productname>Postgres Pro</productname>
14-
9.6.0.1 include:</para>
13+
<para>Major enhancements over <productname>PostgresSQL</productname>
14+
9.6.0 include:</para>
1515
<para>Core patches from PostgresPro 9.5 has been applied:</para>
1616
<itemizedlist>
1717
<listitem>
@@ -40,6 +40,29 @@
4040
</sect2>
4141
<sect2>
4242
<title>Migration to Version 9.6.0.1</title>
43-
<para></para>
43+
44+
<para>A dump/restore using <xref linkend="app-pg-dumpall">, or
45+
use of <xref linkend="pgupgrade">, is required for those
46+
wishing to migrate data from any previous release.</para>
47+
48+
<para>Dump/restore is not neccessary when migrating from PostgreSQL 9.6.x to
49+
Postgres Pro 9.6.x.y.</para>
50+
51+
<para>When upgrading from previous releases of Postgres Pro or from
52+
vanilla PostgreSQL 9.6.x, some catalog changes should be applied.</para>
53+
54+
<para>If you use binary packages, and your database is in the default
55+
location, this upgrade should be performed automatically. If you've
56+
compiled Postgres Pro from source or create your database in
57+
non-default location, running <literal>initdb</literal> manually, you
58+
should run <literal>pgpro_upgrade</literal> script provided in this
59+
distribution.
60+
</para>
61+
62+
<para>Before running script, you should stop postgres service. Script
63+
should be run as user, owning the database (typically postgres) and
64+
PGDATA environment variable should be set to the directory where
65+
database resides.
66+
</para>
4467
</sect2>
4568
</sect1>

0 commit comments

Comments
 (0)