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

Commit 0550987

Browse files
author
Liudmila Mantrova
committed
DOC: sync RNs for 9.6
1 parent 1de92cc commit 0550987

File tree

1 file changed

+158
-0
lines changed

1 file changed

+158
-0
lines changed

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

Lines changed: 158 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,163 @@
11
<!-- doc/src/sgml/release-pro-9.6.sgml -->
22
<!-- See header comment in release.sgml about typical markup -->
3+
<sect1 id="release-pro-9-6-9-1">
4+
<title>Postgres Pro Standard 9.6.9.1</title>
5+
<formalpara>
6+
<title>Release date:</title>
7+
<para>2018-05-18</para>
8+
</formalpara>
9+
<sect2>
10+
<title>Overview</title>
11+
<para>This release is based on <productname>PostgreSQL</productname> 9.6.9
12+
and <productname>Postgres Pro Standard</productname> 9.6.8.2. All improvements
13+
inherited from <productname>PostgreSQL</productname> 9.6.9 are listed
14+
in <link linkend="release-9-6-9"><productname>PostgreSQL</productname> 9.6.9 Release Notes</link>.</para>
15+
<para>Major enhancements over <productname>Postgres Pro Standard</productname>
16+
9.6.8.2 include:</para>
17+
<itemizedlist>
18+
<listitem>
19+
<para>Updated <filename>pg_pathman</filename> module to
20+
version 1.4.11. As compared to version 1.4.9, the following enhancements were introduced:
21+
<itemizedlist>
22+
<listitem>
23+
<para>
24+
Fixed an issue with duplicate entries in query results for inherited tables.
25+
In general, <filename>pg_pathman</filename> does not support multilevel partitioning.
26+
</para>
27+
</listitem>
28+
<listitem>
29+
<para>
30+
Fixed a spurious <literal>table is being partitioned now</literal> error raised
31+
by <function>partition_table_concurrently()</function>.
32+
</para>
33+
</listitem>
34+
<listitem>
35+
<para>
36+
Relaxed check constraint handling.
37+
</para>
38+
</listitem>
39+
<listitem>
40+
<para>
41+
Fixed incorrect usage of <function>memcpy()</function> in <function>start_bgworker()</function>.
42+
</para>
43+
</listitem>
44+
<listitem>
45+
<para>For a full list of changes,
46+
see <ulink url="https://github.com/postgrespro/pg_pathman/releases/"><application>pg_pathman</application> Wiki</ulink>.
47+
</para>
48+
</listitem>
49+
</itemizedlist>
50+
<!--
51+
eb262ce76169f65fff51845b6948aa8b3a339a59
52+
-->
53+
</para>
54+
</listitem>
55+
<listitem>
56+
<para>Updated PTRACK to version 1.5.</para>
57+
<!--
58+
e6f4eb6b2cd4ae0035f50df182f75daf6b375e66
59+
-->
60+
</listitem>
61+
<listitem>
62+
<para>Updated the <xref linkend="mchar"> to fix the sorting order for
63+
Cyrillic letters Yo and short I.
64+
Run the <command>REINDEX</command> command to rebuild indexes
65+
that use <literal>mchar</literal> or <literal>mvarchar</literal> types.</para>
66+
<!-- 67a7654f477a6e3e3beccab054199a49d5c03685 -->
67+
</listitem>
68+
<listitem>
69+
<para>Many fixes for <application>shared_ispell</application> module.</para>
70+
<!-- 5b4a552009d3b4b9b9ab221edc29c97878fa2e83
71+
d544ea69e0bcd4bf5e555c91280666b5c0e51de7
72+
dfbedb881b1db62fc643d8b0305b61ad25f27132
73+
218c3d134377b02eee0e0f738bda3d85695b9032
74+
3e49e0ffb1f197f58d2bf9cc782baa32c58ec6fd
75+
9141db98d86d1d3f24c3e0288d60f2316dddb5ba -->
76+
</listitem>
77+
<listitem>
78+
<para>Improved <productname>Postgres Pro Standard</productname> version for Windows:</para>
79+
<itemizedlist>
80+
<listitem>
81+
<para>Fixed an issue with pasting strings that include symbols
82+
of different character sets from clipboard to psql on Windows systems.</para>
83+
<!-- pgwininstall: 4fc826772ebf0b462c3ef3f8c7626902471c7f8c -->
84+
</listitem>
85+
<listitem>
86+
<para>Updated optimization algorithm for default database configuration.</para>
87+
<!-- pgwininstall: ac9dba438292aabe05ccdc89ff8b1f130292333b -->
88+
</listitem>
89+
<listitem>
90+
<para>Added <literal>needoptimization</literal> option to ini-file based configuration.</para>
91+
<!-- pgwininstall: 8fbed2b264f26f4e7a60d45c145b623a90cb1ff8 -->
92+
</listitem>
93+
</itemizedlist>
94+
</listitem>
95+
</itemizedlist>
96+
</sect2>
97+
<sect2>
98+
<title>Migration to Version 9.6.9.1</title>
99+
100+
<para>Depending on your current installation, the upgrade procedure will differ.
101+
</para>
102+
<para>To upgrade from a <productname>Postgres Pro Standard</productname> version based on
103+
any previous <productname>PostgreSQL</productname> major release, you can perform a dump/restore using
104+
<xref linkend="app-pg-dumpall">, or use the <xref linkend="pgupgrade"> utility.
105+
The first option is safer, while the second is faster and can significantly
106+
speed up the upgrade process for large databases.
107+
</para>
108+
109+
<important>
110+
<para>
111+
When upgrading to version 9.6.9.1, you must call the <command>REINDEX</command>
112+
command for indexes that used <literal>mchar</literal> or <literal>mvarchar</literal> types.
113+
</para>
114+
</important>
115+
116+
<para>To upgrade from a <productname>Postgres Pro Standard</productname> version
117+
based on the same <productname>PostgreSQL</productname> major release,
118+
a dump/restore is not required. If you are upgrading from
119+
<productname>Postgres Pro Standard</productname> 9.6.7.1 or
120+
lower, you must also use the <filename>pgpro_upgrade</filename> script provided
121+
in this distribution. This script updates metadata information to handle
122+
catalog number format change introduced after
123+
<productname>Postgres Pro Standard</productname> 9.6.4.1, as well as
124+
rename the <function>pgpro_build</function> function to <function>pgpro_source_id</function>.
125+
If you are upgrading your
126+
<productname>Postgres Pro</productname> installation from a binary package, the
127+
<filename>pgpro_upgrade</filename> script is run automatically, unless you
128+
are prompted to run it manually.
129+
</para>
130+
<important>
131+
<para>
132+
If you run <literal>pgpro_upgrade</literal> manually,
133+
you must stop postgres service.
134+
The script must be run on behalf of the user owning the database
135+
(typically postgres). Running <literal>pgpro_upgrade</literal>
136+
as root will result in an error.
137+
</para>
138+
</important>
139+
<para>If you have compiled <productname>Postgres Pro</productname>
140+
from source code or created your database in a non-default location,
141+
you must run the <literal>pgpro_upgrade</literal> script manually.
142+
</para>
143+
<note>
144+
<para>On RPM-based Linux distributions, if you are upgrading from
145+
version 9.6.2.1 or lower, make sure to move the data directory from
146+
<filename>pgsql</filename> to the <filename>pgpro</filename>
147+
directory before running the <literal>pgpro_upgrade</literal> script.
148+
</para>
149+
</note>
150+
<para>
151+
After upgrade from version <productname>Postgres Pro Standard</productname>
152+
9.6.8.2 or lesser you must be call <command>REINDEX</command> command
153+
for indexes which used <literal>mchar</literal> or
154+
<literal>mvarchar</literal> types.
155+
</para>
156+
<para>To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore using
157+
<xref linkend="app-pg-dumpall">.
158+
</para>
159+
</sect2>
160+
</sect1>
3161
<sect1 id="release-pro-9-6-8-2">
4162
<title>Postgres Pro Standard 9.6.8.2</title>
5163
<formalpara>

0 commit comments

Comments
 (0)