Skip to content

Commit cf4a24a

Browse files
dmpgprodmpgpro
committed
Update RN
1 parent 5e35a93 commit cf4a24a

File tree

3 files changed

+205
-32
lines changed

3 files changed

+205
-32
lines changed

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

Lines changed: 14 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
<!-- doc/src/sgml/release-pro-9.6.sgml -->
2-
<sect1 id="release-pro-enterprise-9-6-1-2">
3-
<title>&productname; 9.6.1.2</title>
2+
<!-- See header comment in release.sgml about typical markup -->
3+
<sect1 id="release-pro-9-6-2-1">
4+
<title>Postgres Pro 9.6.2.1</title>
45
<note>
56
<title>Release Date</title>
67
<simpara>2017-02-22</simpara>
@@ -12,23 +13,7 @@
1213
<productname>PostgreSQL</productname> <link linkend="release-9-6-2">9.6.2</link>.</para>
1314
<para>Major enhancements over <productname>Postgres Pro</productname>
1415
9.6.1.2 include:</para>
15-
<para>Major enhancements over <productname>Postgres Pro</productname>
16-
9.6.1.2 include:</para>
17-
<para>Added k-nearest neighbors algorithm (KNN) for SP-GiST and B-tree
18-
(See <xref linkend="spgist">)</para>
19-
<para>Added RUM index, based on GIN, as separate module (See <xref linkend="rum">)</para>
20-
<para>WAL size has been reduced on <command>CREATE INDEX</command> operation in the GiST, GIN, SP-GiST</para>
21-
<para>Added timeout for idle sessions on the server side (See <xref linkend="guc-idle-session-timeout">)</para>
22-
<para>Added SHA-2 algorithm for password encryption (See <xref linkend="auth-password">)</para>
23-
<para>Added page level compression (CFS) (See <xref linkend="cfs">)</para>
24-
<para>Added support of autonomous transactions (See <xref linkend="atx">)</para>
25-
<para>Added new optional background worker to schedule tasks by rules (See <xref linkend="pgpro-scheduler">)</para>
26-
<para>Added support for relocatable tables (See <xref linkend="pgtransfer">)</para>
27-
<para>Extension <application>pg_hint_plan</application> has been added (See <xref linkend="pg-hint-plan">)</para>
28-
<para>Transaction IDs on 64-bit platforms use 64-bit data type</para>
29-
<para>Lazy placement of temporary tables on disk</para>
30-
<para>Consistent read on slaves (wait for WAL apply, see <xref linkend="sql-waitlsn">)</para>
31-
<para>Utility <application>pg_repack</application> has been added (See <xref linkend="app-pgrepack">)</para>
16+
3217
<itemizedlist>
3318
<listitem>
3419
<para>Module <link linkend="pg-pathman"><application>pg_pathman</application></link> has been updated to
@@ -80,28 +65,25 @@
8065
</itemizedlist>
8166
</listitem>
8267
</itemizedlist>
68+
8369
</sect2>
8470
<sect2>
85-
<title>Migration to Version &productname; 9.6.1.2</title>
86-
71+
<title>Migration to Version 9.6.2.1</title>
8772
<para>A dump/restore using <xref linkend="app-pg-dumpall">, or
8873
use of <xref linkend="pgupgrade">, is required for those
89-
wishing to migrate data from any previous major release.</para>
90-
91-
<para>Dump/restore is neccessary when migrating from PostgreSQL
92-
or Postgres Pro Standard edition.</para>
93-
94-
<para>When upgrading from previous releases of Postgres Pro or from
95-
vanilla PostgreSQL 9.6.x, some catalog changes should be applied.</para>
96-
74+
wishing to migrate data from any previous major release.
75+
</para>
76+
<para>A dump/restore is not required for those running 9.6.1.2.</para>
77+
<para>However, if you are upgrading from vanilla PostgreSQL 9.6.x, some
78+
catalog changes should be applied.
79+
</para>
9780
<para>If you use binary packages, and your database is in the default
9881
location, this upgrade should be performed automatically. If you've
99-
compiled Postgres Pro from source or create your database in
82+
compiled Postgres Pro from source or create your database in a
10083
non-default location, running <literal>initdb</literal> manually, you
10184
should run <literal>pgpro_upgrade</literal> script provided in this
10285
distribution.
10386
</para>
104-
10587
<para>Before running the script, you should stop postgres service.
10688
Script should be run on behalf of the user owning the database
10789
(typically postgres) and PGDATA environment variable should be
@@ -122,6 +104,7 @@
122104
</para>
123105
<para>Major enhancements over <productname>Postgres Pro</productname>
124106
9.6.1.1 include:</para>
107+
125108
<para>Several modules to support 1C Enterprise added:</para>
126109
<itemizedlist>
127110
<listitem>

‎doc/src/sgml/release-proee-9.6.sgml

Lines changed: 189 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,189 @@
1+
<!-- doc/src/sgml/release-proee-9.6.sgml -->
2+
<sect1 id="release-proee-9-6-2-1">
3+
<title>&productname; 9.6.2.1</title>
4+
<note>
5+
<title>Release Date</title>
6+
<simpara>2017-03-__</simpara>
7+
</note>
8+
<sect2>
9+
<title>Overview</title>
10+
<para>This release is based on <productname>Postgres Pro Enterprise</productname>
11+
<link linkend="release-proee-9-6-1-2">9.6.1.2</link> and
12+
<productname>Postgres Pro Standard</productname> <link linkend="release-pro-9-6-2-1">9.6.2.1</link>.</para>
13+
<para>Major enhancements over <productname>Postgres Pro Enterprise</productname>
14+
9.6.1.2 include:</para>
15+
<itemizedlist>
16+
<!-- Waiting for merge of multimaster:
17+
<listitem><para>Added <application>multimaster</application>
18+
extension. With this extension, you can turn a
19+
<productname>PostgreSQL</productname> master-slave cluster into a
20+
shared-nothing cluster with synchronous multi-master
21+
replication. Such a cluster provides <acronym>OLTP</acronym>
22+
scalability for read transactions, ensures fault tolerance and
23+
automatic node recovery, as well as
24+
enables <productname>PostgreSQL</productname> online
25+
upgrades. (See <xref linkend="multimaster">.)</para>
26+
</listitem>
27+
<listitem><para>Added failover algorithm for <application>libpq</application> connections.</para></listitem>
28+
-->
29+
<listitem><para>Added <application>aqo</application> extension for
30+
adaptive query optimization. Based on the collected statistics on
31+
query execution, <application>aqo</application> improves cardinality
32+
estimation, which can speed up subsequent
33+
queries. (See <xref linkend="aqo">.)</para></listitem>
34+
<listitem><para>Implemented declarative syntax for
35+
partitioning. The <application>pg_pathman</application> extension
36+
can now perform range and hash partitioning as part of
37+
the <command>CREATE TABLE</command> query. Partition management can
38+
be done with various forms of
39+
<command>ALTER
40+
TABLE</command>. (See <xref linkend="pg-pathman-using-declarative-syntax">.)</para>
41+
</listitem>
42+
<listitem><para>Added <application>mamonsu</application> monitoring
43+
service, which is implemented as a <application>Zabbix</application>
44+
agent. Using <application>mamonsu</application>, you can monitor
45+
multiple <productname>PostgreSQL</productname> and system metrics
46+
and visualize the collected data in comprehensive graphs. If
47+
required, you can extend <application>mamonsu</application> with
48+
your own custom plugins. (See <xref linkend="mamonsu">.)</para>
49+
</listitem>
50+
<listitem><para>Added <application>pg_wait_sampling</application>
51+
extension for sampling-based statistics of wait events. With this
52+
extension, you can get an insight into the server activity,
53+
including the current wait events for all processes and background
54+
workers. (See <xref linkend="pg-wait-sampling">.)</para>
55+
</listitem>
56+
<listitem><para>Added support for timestamp output in
57+
the <application>pg_xlogdump</application> extension.</para></listitem>
58+
<listitem>
59+
<para>Added support for one-time background jobs in
60+
<application>pgpro_scheduler</application>. You can now submit jobs
61+
for immediate or delayed one-time execution in parallel with the
62+
scheduled jobs. (See <xref linkend="pgpro-scheduler">.)</para>
63+
</listitem>
64+
<listitem>
65+
<para>Updated
66+
the <link linkend="app-pgprobackup"><application>pg_probackup</application></link>
67+
backup manager to version 1.1.0. This release adds cleanup and
68+
portability fixes.</para>
69+
</listitem>
70+
<listitem>
71+
<para>Improved compressed tablespaces:</para>
72+
<itemizedlist>
73+
<!-- Waiting for the license:
74+
<listitem><para>Replaced <acronym>RC4</acronym> encryption algorithm
75+
with <acronym>AES</acronym>.</para></listitem> -->
76+
<listitem>
77+
<para>Added function <function>cfs_garbage_ratio</function>, which
78+
returns garbage ratio for a given relation.</para></listitem>
79+
<listitem><para>Improved stability on the server hard reset or
80+
process killed by <literal>SIGTERM</literal>.</para></listitem>
81+
</itemizedlist>
82+
</listitem>
83+
<listitem>
84+
<para>Bug Fixes:</para>
85+
<itemizedlist>
86+
<listitem>
87+
<para>Provided a bug fix for k-NN patch (intarray?)</para>
88+
</listitem>
89+
<listitem>
90+
<para>Fixed incorrect <literal>xmin</literal>,
91+
<literal>xmax</literal> values in autonomous
92+
transactions.</para>
93+
</listitem>
94+
<listitem>
95+
<para>Fixed <function>submit_job</function> and
96+
<function>set_job_attribute</function> <application>pgpro_scheduler</application>
97+
functions on Microsoft Windows systems.</para>
98+
</listitem>
99+
<listitem>
100+
<para>Resolved the issue of data corruption in compressed
101+
tablespaces.</para></listitem>
102+
</itemizedlist>
103+
</listitem>
104+
</itemizedlist>
105+
</sect2>
106+
<sect2>
107+
<title>Migration to Version &productname; 9.6.2.1</title>
108+
109+
<para>A dump/restore using <xref linkend="app-pg-dumpall">, or
110+
use of <xref linkend="pgupgrade">, is required for those
111+
wishing to migrate data from any previous major release.</para>
112+
113+
<para>Dump/restore is neccessary when migrating from <productname>PostgreSQL</productname>
114+
or <productname>Postgres Pro Standard</productname> edition.</para>
115+
116+
<para>For upgrades from previous releases of <productname>Postgres Pro</productname> or
117+
PostgreSQL 9.6.x, some catalog changes should be applied.</para>
118+
119+
<para>If you use binary packages, and your database is in the default
120+
location, this upgrade should be performed automatically. If you've
121+
compiled <productname>Postgres Pro</productname> from source or created your database in
122+
a non-default location running <literal>initdb</literal> manually, you
123+
should run the <literal>pgpro_upgrade</literal> script provided in this
124+
distribution.
125+
</para>
126+
127+
<para>Before running the script, you should stop the <literal>postgres</literal> service.
128+
The script should be run on behalf of the user owning the database
129+
(typically <literal>postgres</literal>), and the <envar>PGDATA</envar> environment variable should be
130+
set to the directory where the database resides.
131+
</para>
132+
</sect2>
133+
</sect1>
134+
<sect1 id="release-proee-9-6-1-2">
135+
<title>&productname; 9.6.1.2</title>
136+
<note>
137+
<title>Release Date</title>
138+
<simpara>2016-12-15</simpara>
139+
</note>
140+
<sect2>
141+
<title>Overview</title>
142+
<para>This release is based on <productname>Postgres Pro</productname>
143+
<link linkend="release-pro-9-6-1-2">9.6.1.2</link></para>
144+
<para>Major enhancements over <productname>Postgres Pro</productname>
145+
9.6.1.2 include:</para>
146+
<para>Added k-nearest neighbors algorithm (KNN) for SP-GiST and B-tree
147+
(See <xref linkend="spgist">)</para>
148+
<para>Added RUM index, based on GIN, as separate module (See <xref linkend="rum">)</para>
149+
<para>WAL size has been reduced on <command>CREATE INDEX</command> operation in the GiST, GIN, SP-GiST</para>
150+
<para>Added timeout for idle sessions on the server side (See <xref linkend="guc-idle-session-timeout">)</para>
151+
<para>Added SHA-2 algorithm for password encryption (See <xref linkend="auth-password">)</para>
152+
<para>Added page level compression (CFS) (See <xref linkend="cfs">)</para>
153+
<para>Added support of autonomous transactions (See <xref linkend="atx">)</para>
154+
<para>Added new optional background worker to schedule tasks by rules (See <xref linkend="pgpro-scheduler">)</para>
155+
<para>Added support for relocatable tables (See <xref linkend="pgtransfer">)</para>
156+
<para>Extension <application>pg_hint_plan</application> has been added (See <xref linkend="pg-hint-plan">)</para>
157+
<para>Transaction IDs on 64-bit platforms use 64-bit data type</para>
158+
<para>Lazy placement of temporary tables on disk</para>
159+
<para>Consistent read on slaves (wait for WAL apply, see <xref linkend="sql-waitlsn">)</para>
160+
<para>Utility <application>pg_repack</application> has been added (See <xref linkend="app-pgrepack">)</para>
161+
</sect2>
162+
<sect2>
163+
<title>Migration to Version &productname; 9.6.1.2</title>
164+
165+
<para>A dump/restore using <xref linkend="app-pg-dumpall">, or
166+
use of <xref linkend="pgupgrade">, is required for those
167+
wishing to migrate data from any previous major release.</para>
168+
169+
<para>Dump/restore is neccessary when migrating from PostgreSQL
170+
or Postgres Pro Standard edition.</para>
171+
172+
<para>When upgrading from previous releases of Postgres Pro or from
173+
vanilla PostgreSQL 9.6.x, some catalog changes should be applied.</para>
174+
175+
<para>If you use binary packages, and your database is in the default
176+
location, this upgrade should be performed automatically. If you've
177+
compiled Postgres Pro from source or create your database in
178+
non-default location, running <literal>initdb</literal> manually, you
179+
should run <literal>pgpro_upgrade</literal> script provided in this
180+
distribution.
181+
</para>
182+
183+
<para>Before running script, you should stop postgres service. Script
184+
should be run as user, owning the database (typically postgres) and
185+
PGDATA environment variable should be set to the directory where
186+
database resides.
187+
</para>
188+
</sect2>
189+
</sect1>

‎doc/src/sgml/release.sgml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,8 @@ For new features, add links to the documentation sections.
7272

7373
The reason for splitting the release notes this way is so that appropriate
7474
subsets can easily be copied into back branches.
75-
-->
75+
-->
76+
&release-proee-9.6;
7677
&release-pro-9.6;
7778
&release-9.6;
7879
&release-9.5;

0 commit comments

Comments
 (0)