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

Commit 0d147d1

Browse files
author
Liudmila Mantrova
committed
DOC: added first version of PGPROEE10 release notes
1 parent a1b019f commit 0d147d1

File tree

3 files changed

+359
-0
lines changed

3 files changed

+359
-0
lines changed

‎doc/src/sgml/filelist.sgml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -196,6 +196,7 @@
196196
<!ENTITY sourcerepo SYSTEM "sourcerepo.sgml">
197197

198198
<!ENTITY release SYSTEM "release.sgml">
199+
<!ENTITY release-proee-10 SYSTEM "release-proee-10.sgml">
199200
<!ENTITY release-pro-10 SYSTEM "release-pro-10.sgml">
200201
<!ENTITY release-pro-9.6 SYSTEM "release-pro-9.6.sgml">
201202
<!ENTITY release-pro-9.5 SYSTEM "release-pro-9.5.sgml">

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

Lines changed: 357 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,357 @@
1+
<!-- doc/src/sgml/release-proee-10.sgml -->
2+
<sect1 id="release-proee-10-1-1">
3+
<title>&productname; 10.1.1</title>
4+
<formalpara>
5+
<title>Release date:</title>
6+
<para>2018-02-02</para>
7+
</formalpara>
8+
<sect2>
9+
<title>Overview</title>
10+
<para>This release is based on <productname>Postgres Pro</productname> 10.1.1
11+
and <productname>Postgres Pro Enterprise</productname> 9.6.6.3.
12+
As compared with <productname>Postgres Pro Enterprise</productname> 9.6.6.3,
13+
this version adds the following new features:</para>
14+
<itemizedlist>
15+
<listitem>
16+
<para>
17+
<filename>pg_shardman</filename>. This experimental extension
18+
enables sharding, aiming for scalability and fault tolerance
19+
with transaction support. It provides best results for
20+
<acronym>OLTP</acronym> workloads.
21+
</para>
22+
</listitem>
23+
<listitem>
24+
<para>
25+
<filename>in-memory</filename>. This extension
26+
enables you to store data in <productname>&productname;</productname>
27+
shared memory. (See <xref linkend="in-memory">.)
28+
</para>
29+
</listitem>
30+
<listitem>
31+
<para>
32+
<filename>vops</filename>. This extension enables vertical data model
33+
for &productname;. It can speed up <acronym>OLAP</acronym> queries
34+
with filtering and aggregation by times.
35+
</para>
36+
</listitem>
37+
<listitem>
38+
<para>
39+
Declarative syntax for partitioning uses <filename>pg_pathman</filename>
40+
as the default partitioning engine.
41+
(See <xref linkend="pg-pathman-using-declarative-syntax">.)
42+
</para>
43+
</listitem>
44+
<listitem>
45+
<para>
46+
SCRAM-SHA-256 algorithm implementation for password encryption is replaced
47+
with the one introduced in vanilla <productname>PostgreSQL</productname>.
48+
(See <xref linkend="auth-password">.)
49+
</para>
50+
</listitem>
51+
<listitem>
52+
<para>
53+
Failover algorithm for libpq connections is replaced with
54+
vanilla <productname>PostgreSQL</productname> implementation.
55+
</para>
56+
</listitem>
57+
<listitem>
58+
<para>
59+
Unified the structure of binary installation packages across all
60+
Linux-based distributions. The new package structure differs from
61+
that of vanilla <productname>PostgreSQL</productname>, but offers
62+
the following benefits:
63+
<itemizedlist>
64+
<listitem>
65+
<para>
66+
You do not need to worry about installation specifics on different
67+
Linux distributions when migrating between different supported Linux systems.
68+
<productname>Postgres Pro Enterprise</productname> is now installed
69+
to the <filename>/opt/pgpro/ent-&majorversion;</filename> directory,
70+
while the default database is created in the
71+
<filename>/var/lib/pgpro/ent-&majorversion;/data</filename> directory.
72+
</para>
73+
</listitem>
74+
<listitem>
75+
<para>
76+
You can now fully control the default database creation on all Linux distributions.
77+
If you install the <filename>postgrespro-ent-&majorversion;</filename>
78+
package, it deploys all the <productname>Postgres Pro Enterprise</productname>
79+
packages required for your system, creates the default database,
80+
and configures the server in a fully automated way.
81+
If you install individual packages, you need to configure
82+
<productname>Postgres Pro Enterprise</productname> yourself.
83+
In this case, you have to manually initialize
84+
the database cluster and start the server, as well as configure
85+
automatic server startup if required.
86+
</para>
87+
</listitem>
88+
<listitem>
89+
<para>
90+
You can install <productname>Postgres Pro Enterprise</productname> 10
91+
side by side with other <productname>PostgreSQL</productname>-based products
92+
for seamless migration or parallel work. If you are using individual
93+
packages, your current system configuration will be preserved,
94+
so you have to manually configure <productname>Postgres Pro Enterprise</productname>,
95+
as explained in <xref linkend="custom-pgpro-install">. Do not install
96+
the <filename>postgrespro-ent-&majorversion;</filename> package on the
97+
same system with other <productname>PostgreSQL</productname>-based products
98+
to avoid conflicts.
99+
</para>
100+
</listitem>
101+
</itemizedlist>
102+
Note that <filename>postgrespro-common</filename>
103+
and <filename>postgrespro-client-common</filename>
104+
packages are no longer available on Debian-based systems.
105+
For details, see <xref linkend="binary-installation-on-linux">.
106+
</para>
107+
</listitem>
108+
</itemizedlist>
109+
<para>
110+
The following features have been ported from <productname>Postgres Pro Enterprise</productname> 9.6.6.3:
111+
</para>
112+
<itemizedlist>
113+
<listitem>
114+
<para>
115+
<filename>aqo</filename> extension for adaptive query optimization.
116+
(See <xref linkend="aqo">.)
117+
<!--
118+
1cb5e489cc7f8a049ed89259aa548dd832d2f354
119+
-->
120+
</para>
121+
</listitem>
122+
<listitem>
123+
<para>
124+
<filename>multimaster</filename> and <filename>referee</filename> extensions.
125+
(See <xref linkend="multimaster"> and <xref linkend="referee">, respectively.)
126+
</para>
127+
</listitem>
128+
<listitem>
129+
<para>Extension <application>pg_hint_plan</application> has been added (See <xref linkend="pg-hint-plan">)</para>
130+
<!--
131+
697b10f94245110c8f7a2b70d9750eea4ee9c0e0
132+
1b8a467426b045a124d88ea13c38365ba48770ad
133+
b222a0a2055a1d178d52f7cf71f69823c92ae9bc
134+
e63e35881a4f77ea804377baa26c8aff571341bc
135+
-->
136+
</listitem>
137+
<listitem>
138+
<para><filename>pgpro_scheduler</filename> (See <xref linkend="pgpro-scheduler">.)</para>
139+
<!--
140+
5b026af712d6b0f345eeaf8114a9e82bdb1f75a7
141+
-->
142+
</listitem>
143+
<listitem>
144+
<para><application>pg_tsparser</application> text search parser.
145+
(See <xref linkend="pg-tsparser">.)</para>
146+
</listitem>
147+
<listitem>
148+
<para>
149+
<filename>pg_wait_sampling</filename> extension for sampling-based statistics of wait events.
150+
(See <xref linkend="pg-wait-sampling">.)
151+
<!--
152+
811989ebc36b5e72a78d7112f9b02b6a465802b1
153+
a6d6460cf6e93497f7212d05c4ddb140aed08072
154+
-->
155+
</para>
156+
</listitem>
157+
<listitem>
158+
<para>RUM index, based on GIN. (See <xref linkend="rum">.)</para>
159+
<!--
160+
002356c72631587bf957539b6f70031084eeda3e
161+
32f221a21829aae9a6eed2f6cc946944aca0f19c
162+
d37b213f93bf73a1a915313807009853f0a12c95
163+
10e2ea6720a55713e8fbd9ae31753863b741c763
164+
0508b961dc195909ba6f5568d7644ec87ffe472e
165+
a1da82601622a3ff3d6077b0d76c7244a42196c0
166+
c1df4cc1ec1d86b5a06f28dfb0a8360a6f2f652c
167+
-->
168+
</listitem>
169+
<listitem>
170+
<para>Timeout for idle sessions on the server side. (See <xref linkend="guc-idle-session-timeout">.)</para>
171+
<!--
172+
26950fecb4a6dc2c80f1089dd10dfbe3c1b6229a
173+
-->
174+
</listitem>
175+
<listitem>
176+
<para>Page-level compression (CFS). (See <xref linkend="cfs">.)</para>
177+
<!--
178+
b251edf6dd4e7b5ffffced5493d5451e7cab86f6
179+
-->
180+
</listitem>
181+
<listitem>
182+
<para>Autonomous transactions support. (See <xref linkend="atx">.)</para>
183+
<!--
184+
dd5cf8c150257d4c8f64781ee492553ad067b8c3
185+
9fe8b50637924e4c067ee97b7ed12e09fc3ad0ae
186+
-->
187+
</listitem>
188+
<listitem>
189+
<para>Support for relocatable tables (See <xref linkend="pgtransfer">)</para>
190+
<!--
191+
4c4feef5e9ad40d59a14b3277cc52977043987ce
192+
-->
193+
</listitem>
194+
<listitem>
195+
<para>Transaction IDs on 64-bit platforms use 64-bit data type</para>
196+
<!--
197+
0a9293c8e045ae94ded1f6072716ddad8a3d6ced
198+
efd552ee5c188f1d7039a09190575edcd42de031
199+
37f1e1b017a1de600b7b4162af7db7869c742e40
200+
efbdcbd80c3bc156f9f25c1dc6b995df434e05e7
201+
474a8b0beee97685b5c5183c34b007263e22c728
202+
b22c29989c10a4da95028074a98f3afb61130837
203+
7aa2ca79479936b7239211e3e45d20e438d2eb3f
204+
5c96769e83a4700621b2a99415480a8b96d8c0b4
205+
54996dd6c4307ccfade8ba7affb0502a249515d0
206+
b208264d6f376ad11e43b2528c8302c95c1b7e15
207+
-->
208+
</listitem>
209+
<listitem>
210+
<para>Consistent reads on standby servers. (See <xref linkend="sql-waitlsn">.)</para>
211+
<!--
212+
ba5e8511125908577e6fd4c4b0eba65ab793ae15
213+
d7b584c8aa14772fd5f2c5c391dc2bb14c5139a9
214+
9881464b76750333c04b3fd3ad47173761d8ad8b
215+
-->
216+
</listitem>
217+
<listitem>
218+
<para><application>pg_repack</application> utility. (See <xref linkend="app-pgrepack">.)</para>
219+
</listitem>
220+
<listitem>
221+
<para>
222+
K-nearest neighbor (k-NN) algorithm support for B-tree, GiST, and SP-GiST index types.
223+
(See <xref linkend="k-nn-search">.)
224+
<!--
225+
9e330ae24849902dcffce8fadf6e5c177e9f00f7
226+
-->
227+
</para>
228+
</listitem>
229+
<listitem>
230+
<para><application>mamonsu</application> monitoring
231+
service, which is implemented as a <application>Zabbix</application>
232+
agent. (See <xref linkend="mamonsu">.)</para>
233+
</listitem>
234+
<listitem>
235+
<para>
236+
Handling transactions with serialization or deadlock errors in <application>pg_bench</application>.
237+
<!--
238+
81a4ee1ddffa20f1b738b3c3ccde8611b9b92ee8
239+
-->
240+
</para>
241+
</listitem>
242+
</itemizedlist>
243+
<para>
244+
All features and enhancements inherited from <productname>Postgres Pro</productname> 10.1.1 are listed
245+
in <link linkend="release-pro-10-1-1"><productname>Postgres Pro</productname> 10.1.1 Release Notes</link>.
246+
</para>
247+
</sect2>
248+
249+
<sect2>
250+
<title>Migration to Version 10.1.1</title>
251+
252+
<para>
253+
To migrate to <productname>Postgres Pro Enterprise</productname> 10,
254+
you are recommended to perform a dump/restore using
255+
<xref linkend="app-pg-dumpall">. Using <xref linkend="pgupgrade"> utility
256+
can only used when upgrading from <productname>Postgres Pro Enterprise</productname> 9.6 versions.
257+
</para>
258+
259+
<para>
260+
When migrating to <productname>Postgres Pro Enterprise</productname> 10, do not
261+
use the <filename>postgrespro-ent-&majorversion;</filename>
262+
package to avoid conflicts. Use the individual packages instead.
263+
In this case, server autostart needs to be enabled manually, if required.
264+
</para>
265+
266+
<para>Starting from <productname>Postgres Pro Enterprise</productname> 10, you can specify the
267+
default collation provider when initializing the database cluster or
268+
creating the database, as explained in <xref linkend="collation-managing">.
269+
You must take it into account when upgrading to this release
270+
to avoid breaking indexes and constraints.
271+
</para>
272+
<important>
273+
<para>
274+
If your current <productname>Postgres Pro Enterprise</productname> installation
275+
uses ICU, do not update ICU library to a newer version.
276+
Otherwise, you cannot upgrade to <productname>Postgres Pro Enterprise</productname> 10.
277+
</para>
278+
</important>
279+
<important>
280+
<para>
281+
For <productname>PostgreSQL</productname> 9.5 and 9.5.1,
282+
as well as <productname>Postgres Pro</productname> 9.5.0.1 and
283+
9.5.1.2, you cannot perform an upgrade to
284+
<productname>Postgres Pro Enterprise</productname> 10 directly. If you are
285+
using one of these versions, upgrade your installation to an
286+
intermediate version first, such as
287+
<productname>Postgres Pro</productname> 9.5.2.1.
288+
</para>
289+
</important>
290+
291+
<para>
292+
When you are using <xref linkend="app-pg-dumpall">
293+
to perform the upgrade, <productname>Postgres Pro</productname> uses
294+
the collation provider specified with the <command>initdb</command>
295+
command for the new cluster. In this case, indexes are rebuilt
296+
automatically. To avoid issues with collation-dependent constraints,
297+
you are recommended to use <literal>libc</literal> provider when
298+
upgrading from vanilla <productname>PostgreSQL</productname>, and
299+
omit the provider when upgrading from a previous version of
300+
<productname>Postgres Pro</productname>, unless you have databases with
301+
non-C and non-POSIX collation settings. For such databases, you should
302+
do the following:
303+
<itemizedlist>
304+
<listitem>
305+
<para>If the new cluster is initialized with locales other than C or POSIX,
306+
and the database has an single-byte encoding, set LC_COLLATE to '@libc' for this database.
307+
</para>
308+
</listitem>
309+
<listitem>
310+
<para>If the new cluster is initialized with C or POSIX locale settings and
311+
the database has a multi-byte encoding, set LC_COLLATE to <literal>'@icu'</literal> for this database.
312+
</para>
313+
</listitem>
314+
</itemizedlist>
315+
</para>
316+
317+
<note>
318+
<para>
319+
If the previous <productname>Postgres Pro</productname> installation
320+
contained any indexes or constraints depending on collations
321+
other than the default collation of the database, <literal>C</literal>,
322+
or <literal>POSIX</literal> in databases with multibyte encodings,
323+
such databases could contain some data that violated the specified
324+
constraints and made indexes inconsistent. On Windows, this situation
325+
can also happen if the database with a multibyte encoding contained
326+
any indexes or constraints depending on the default collation with a
327+
verbose name, such as
328+
<literal>"Russian_Russia[.<replaceable>encoding</replaceable>]"</literal>
329+
or <literal>"English_United
330+
States[.<replaceable>encoding</replaceable>]"</literal>.
331+
In such cases, you can only use <application>pg_upgrade</application> to upgrade to
332+
<productname>Postgres Pro</productname> 10, as a dump/restore scenario may be impossible.
333+
To resolve these issues, <application>pg_upgrade</application> declares such indexes and
334+
constraints invalid and creates <filename>reindex_text_indexes.sql</filename>
335+
and <filename>validate_text_contraints.sql</filename>, respectively.
336+
</para>
337+
</note>
338+
339+
<para>
340+
If you choose to run <application>pg_upgrade</application> when upgrading
341+
from <productname>Postgres Pro Enterprise</productname> 9.6 versions,
342+
make sure to initialize the new database cluster with the same
343+
<link linkend="app-initdb-data-checksums">checksum setting</link>
344+
as the database cluster you are migrating from. To ensure that
345+
that <xref linkend="APP-INITDB"> sets the correct default collation provider
346+
for the new database cluster, omit the default collation provider
347+
option to select the required collation
348+
provider automatically. In this case, <literal>libc</literal> provider
349+
will be used for databases with C and POSIX locales, as well as for all
350+
databases with single-byte encodings, while <literal>icu</literal>
351+
provider will be used for all the other cases.
352+
If <application>pg_upgrade</application> creates any SQL files in
353+
its current directory, run these files to complete the upgrade.
354+
</para>
355+
356+
</sect2>
357+
</sect1>

‎doc/src/sgml/release.sgml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,7 @@ For new features, add links to the documentation sections.
6464
The reason for splitting the release notes this way is so that appropriate
6565
subsets can easily be copied into back branches.
6666
-->
67+
&release-proee-10;
6768
&release-pro-10;
6869
&release-pro-9.6;
6970
&release-pro-9.5;

0 commit comments

Comments
 (0)