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

Commit 03b29cf

Browse files
dmpgprodmpgpro
committed
Added RN 10.2.1
1 parent ebc7566 commit 03b29cf

File tree

1 file changed

+182
-0
lines changed

1 file changed

+182
-0
lines changed

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

Lines changed: 182 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,188 @@
11
<!-- doc/src/sgml/release-pro-10.sgml -->
22
<!-- See header comment in release.sgml about typical markup -->
3+
<sect1 id="release-pro-10-2-1">
4+
<title>Postgres Pro 10.2.1</title>
5+
<formalpara>
6+
<title>Release Date:</title>
7+
<para>2018-02-16</para>
8+
</formalpara>
9+
<sect2>
10+
<title>Overview</title>
11+
<para>This release is based on <productname>PostgreSQL</productname> 10.2
12+
and includes all the new features introduced in PostgreSQL 10, as well as
13+
bug fixes implemented in PostgreSQL 10.2. For their detailed description,
14+
see <link linkend="release-10">PostgreSQL 10 Release Notes</link> and
15+
<link linkend="release-10-2">PostgreSQL 10.2 Release Notes</link>, respectively.
16+
Other major changes and enhancements are as follows:</para>
17+
<itemizedlist spacing="compact">
18+
<listitem>
19+
<para>
20+
Added support for TOAST to INCLUDED attributes for B-tree indexes.</para>
21+
<!--
22+
82b20c67ee951030bc1791bfaecde7ca8aeb913f
23+
303a732208a8301827268d10f2248a00cffaf348
24+
-->
25+
</listitem>
26+
<listitem>
27+
<para>Implemented dynamic prepare of the <command>psql</command> history path on Windows systems.</para>
28+
<!--
29+
e80337e33aa37839e1a141f6d196096e1148cf17
30+
5850209dbff28912d1da44bcfab23f0e16907667
31+
-->
32+
</listitem>
33+
<listitem>
34+
<para>Updated the <link linkend="app-pgprobackup"><application>pg_probackup</application></link>
35+
utility to version 2.0.14.</para>
36+
<!-- fc40ff8949f10e50e0aaf805f69082539176626b -->
37+
</listitem>
38+
<listitem>
39+
<para>Module <application>pg_variables</application> has been updated.</para>
40+
<!-- 8829bc249562295bf212ce1021bf6a41da6fe0c7 -->
41+
</listitem>
42+
<listitem>
43+
<para>Updated <xref linkend="pg-pathman"> module to
44+
version 1.4.9. This version fixes handling of <literal>ONLY</literal>
45+
in all kinds of queries.
46+
(See <xref linkend="pg-pathman"> and <xref linkend="pg-pathman-how-to-update">.)
47+
</para>
48+
<!-- 9e2652b115276ce309a089ba2289572faad98e37 -->
49+
</listitem>
50+
<listitem>
51+
<para>Updated <application>dump_stat</application> module to
52+
version 1.1 that provides several bug fixes.
53+
(See <xref linkend="dump-stat">.)</para>
54+
<!-- efb70c83ccdead1e1d3604ec67eeae16c9fd26e5 -->
55+
</listitem>
56+
<listitem>
57+
<para>Fixed incorrect handling of <literal>IS NULL / IS NOT NULL</literal>
58+
quals in the indexes with included columns.</para>
59+
<!-- 7bfe5275e91817dca49dd6e773130473e76c8183 -->
60+
</listitem>
61+
<listitem>
62+
<para>Added <literal>int2vector</literal> compatibility patch.</para>
63+
<!-- 0fc6e45196e78f479aa0fe95d5ff31aab6c67768 -->
64+
</listitem>
65+
<listitem>
66+
<para>Module <application>online-analyze</application> has been
67+
updated.</para>
68+
<!-- adce42211d871c834d8ce339a241f866feb1a84b -->
69+
</listitem>
70+
</itemizedlist>
71+
</sect2>
72+
<sect2>
73+
<title>Migration to Version 10.2.1</title>
74+
75+
<para>
76+
To migrate to <productname>Postgres Pro</productname> 10, you can perform a dump/restore using
77+
<xref linkend="app-pg-dumpall">, or use the <xref linkend="pgupgrade"> utility.
78+
The first option is safer, while the second is faster and can significantly
79+
speed up the upgrade process for large databases. If you choose to run
80+
<application>pg_upgrade</application>, make sure to initialize the new
81+
database cluster with the same <link linkend="app-initdb-data-checksums">checksum setting</link>
82+
as the database cluster you are migrating from.
83+
</para>
84+
85+
<para>
86+
When migrating to <productname>Postgres Pro</productname> 10, do not
87+
use the <filename>postgrespro-std-&majorversion;</filename>
88+
package to avoid conflicts. Use the individual packages instead.
89+
In this case, server autostart needs to be enabled manually, if required.
90+
</para>
91+
92+
<para>Starting from <productname>Postgres Pro</productname> 10, you can specify the
93+
default collation provider when initializing the database cluster or
94+
creating the database, as explained in <xref linkend="collation-managing">.
95+
You must take it into account when upgrading to this release
96+
to avoid breaking indexes and constraints.
97+
</para>
98+
99+
<important>
100+
<para>
101+
If your current <productname>Postgres Pro</productname> installation
102+
uses ICU, do not update ICU library to a newer version.
103+
Otherwise, you cannot upgrade to <productname>Postgres Pro</productname> 10.
104+
</para>
105+
</important>
106+
<important>
107+
<para>
108+
For <productname>PostgreSQL</productname> 9.5 and 9.5.1,
109+
as well as <productname>Postgres Pro</productname> 9.5.0.1 and
110+
9.5.1.2, you cannot perform an upgrade to
111+
<productname>Postgres Pro</productname> 10 directly. If you are
112+
using one of these versions, upgrade your installation to an
113+
intermediate version first, such as
114+
<productname>Postgres Pro</productname> 9.5.2.1.
115+
</para>
116+
</important>
117+
118+
<para>
119+
When using <xref linkend="pgupgrade">, make sure that
120+
<xref linkend="APP-INITDB"> sets the correct default collation provider
121+
for the new database cluster:
122+
</para>
123+
<itemizedlist>
124+
<listitem>
125+
<para>When migrating from vanilla <productname>PostgreSQL</productname>, specify <literal>libc</>
126+
as the default collation provider.
127+
</para>
128+
</listitem>
129+
<listitem>
130+
<para>When upgrading from <productname>Postgres Pro</productname>, omit
131+
the default collation provider option to select the required collation
132+
provider automatically. In this case, <literal>libc</literal> provider
133+
will be used for databases with C and POSIX locales, as well as for all
134+
databases with single-byte encodings, while <literal>icu</literal>
135+
provider will be used for all the other cases.
136+
</para>
137+
</listitem>
138+
</itemizedlist>
139+
<para>If <application>pg_upgrade</application> creates any SQL files in
140+
its current directory, run these files to complete the upgrade.
141+
</para>
3142

143+
<para>
144+
When you are using <xref linkend="app-pg-dumpall">
145+
to perform the upgrade, <productname>Postgres Pro</productname> uses
146+
the collation provider specified with the <command>initdb</command>
147+
command for the new cluster. In this case, indexes are rebuilt
148+
automatically. To avoid issues with collation-dependent constraints,
149+
you are recommended to use <literal>libc</literal> provider when
150+
upgrading from vanilla <productname>PostgreSQL</productname>, and
151+
omit the provider when upgrading from a previous version of
152+
<productname>Postgres Pro</productname>.
153+
</para>
154+
155+
<note>
156+
<para>
157+
If the previous <productname>Postgres Pro</productname> installation
158+
contained any indexes or constraints depending on collations
159+
other than the default collation of the database, <literal>C</literal>,
160+
or <literal>POSIX</literal> in databases with multibyte encodings,
161+
such databases could contain some data that violated the specified
162+
constraints and made indexes inconsistent. On Windows, this situation
163+
can also happen if the database with a multibyte encoding contained
164+
any indexes or constraints depending on the default collation with a
165+
verbose name, such as
166+
<literal>"Russian_Russia[.<replaceable>encoding</replaceable>]"</literal>
167+
or <literal>"English_United
168+
States[.<replaceable>encoding</replaceable>]"</literal>.
169+
In such cases, you can only use <application>pg_upgrade</application> to upgrade to
170+
<productname>Postgres Pro</productname> 10, as a dump/restore scenario may be impossible.
171+
To resolve these issues, <application>pg_upgrade</application> declares such indexes and
172+
constraints invalid and creates <filename>reindex_text_indexes.sql</filename>
173+
and <filename>validate_text_contraints.sql</filename>, respectively.
174+
</para>
175+
</note>
176+
177+
<para>
178+
When building <productname>Postgres Pro</> manually, you must include ICU
179+
using the <option>--with-icu</option> option. Otherwise, you cannot
180+
upgrade to <productname>Postgres Pro</productname> 10 from a previous
181+
<productname>Postgres Pro</productname> version.
182+
</para>
183+
184+
</sect2>
185+
</sect1>
4186
<sect1 id="release-pro-10-1-1">
5187
<title>Postgres Pro 10.1.1</title>
6188
<formalpara>

0 commit comments

Comments
 (0)