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

Commit 300c422

Browse files
author
Liudmila Mantrova
committed
DOC: sync 9.6 release notes
1 parent 929050a commit 300c422

File tree

1 file changed

+154
-1
lines changed

1 file changed

+154
-1
lines changed

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

Lines changed: 154 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,158 @@
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-6-1">
4+
<title>Postgres Pro 9.6.6.1</title>
5+
<formalpara>
6+
<title>Release date:</title>
7+
<para>2017-11-14</para>
8+
</formalpara>
9+
<sect2>
10+
<title>Overview</title>
11+
<para>This release is based on <productname>PostgreSQL</productname> 9.6.6
12+
and <productname>Postgres Pro</productname> 9.6.5.1. All improvements
13+
inherited from <productname>PostgreSQL</productname> 9.6.6 are listed
14+
in <link linkend="release-9-6-6"><productname>PostgreSQL</productname> 9.6.6 Release Notes</link>.</para>
15+
<para>Major enhancements over <productname>Postgres Pro</productname>
16+
9.6.5.1 include:</para>
17+
<itemizedlist>
18+
<listitem>
19+
<para>Updated <application>pg_pathman</application> module to
20+
version 1.4.8. (See <xref linkend="pg-pathman"> and <xref linkend="pg-pathman-how-to-update">.)
21+
As compared to version 1.4.3, the following enhancements were introduced:
22+
<itemizedlist spacing="compact">
23+
<listitem>
24+
<para>
25+
Improved cache invalidation mechanisms.
26+
</para>
27+
</listitem>
28+
<listitem>
29+
<para>
30+
Disabled <command>COPY <replaceable>partitioned_table</replaceable> TO</command> command.
31+
Use <command>COPY (SELECT * FROM <replaceable>partitioned_table</replaceable>) TO</command> instead.
32+
</para>
33+
</listitem>
34+
<listitem>
35+
<para>
36+
Fixed <command>INSTEAD OF</command> triggers on views selected from partitioned tables.
37+
</para>
38+
</listitem>
39+
<listitem>
40+
<para>
41+
<command>ALTER TABLE <replaceable>partitioned_table</replaceable> RENAME TO</command> now also renames auto naming sequences.
42+
</para>
43+
</listitem>
44+
<listitem>
45+
<para>
46+
Disabled some dangerous optimizations for <command>SELECT ... FOR SHARE/UPDATE</command>
47+
on <productname>PostgreSQL</productname> 9.5.
48+
</para>
49+
</listitem>
50+
<listitem>
51+
<para>
52+
Improved error handling in concurrent partitioning background worker.
53+
</para>
54+
</listitem>
55+
<listitem>
56+
<para>Prohibited execution of queries
57+
<command>DELETE FROM <replaceable>partitioned_table_1</replaceable> USING <replaceable>partitioned_table_2</replaceable>...</command>
58+
and
59+
<command>UPDATE <replaceable>partitioned_table_1</replaceable> FROM <replaceable>partitioned_table_2</replaceable>...</command>
60+
if such queries touch more than one partition of <replaceable>partitioned_table_1</replaceable>.
61+
</para>
62+
</listitem>
63+
<listitem>
64+
<para>Fixed a bug causing crashes on <command>RESET ALL</command>.</para>
65+
</listitem>
66+
<listitem>
67+
<para>Fixed <literal>WHERE</literal> conditions that point to gaps between partitions.</para>
68+
</listitem>
69+
<listitem>
70+
<para>Restored compatibility with <application>pg_repack</application>.</para>
71+
</listitem>
72+
<listitem>
73+
<para>For the full list of changes,
74+
see <ulink url="https://github.com/postgrespro/pg_pathman/releases/"><application>pg_pathman</application> Wiki</ulink>.
75+
</para>
76+
</listitem>
77+
</itemizedlist>
78+
</para>
79+
</listitem>
80+
<listitem>
81+
<para>Updated
82+
the <link linkend="app-pgprobackup"><application>pg_probackup</application></link>
83+
utility from version 2.0.2 to 2.0.11, which includes the following new features:</para>
84+
<itemizedlist>
85+
<listitem>
86+
<para>Password prompt interruption is now handled correctly.</para>
87+
</listitem>
88+
<listitem>
89+
<para>The provided passwords are checked to be is non-empty.</para>
90+
</listitem>
91+
<listitem>
92+
<para>
93+
The files that have not changed since the previous backup
94+
are not included into the next incremental backup.
95+
</para>
96+
</listitem>
97+
<listitem>
98+
<para>Database version is now added into backup meta information.</para>
99+
</listitem>
100+
<listitem>
101+
<para>Other miscellaneous bugfixes.</para>
102+
</listitem>
103+
</itemizedlist>
104+
</listitem>
105+
</itemizedlist>
106+
</sect2>
107+
<sect2>
108+
<title>Migration to Version 9.6.6.1</title>
109+
<para>Depending on your current installation, the upgrade procedure will differ.
110+
</para>
111+
<para>To upgrade from a <productname>Postgres Pro</productname> version based on
112+
any previous <productname>PostgreSQL</productname> major release, you can perform a dump/restore using
113+
<xref linkend="app-pg-dumpall">, or use the <xref linkend="pgupgrade"> utility.
114+
The first option is safer, while the second is faster and can significantly
115+
speed up the upgrade process for large databases.
116+
</para>
117+
<para>To upgrade from a <productname>Postgres Pro</productname> version
118+
based on the same <productname>PostgreSQL</productname> major release,
119+
a dump/restore is not required. If you are upgrading from
120+
<productname>Postgres Pro</productname> 9.6.5.1, it is enough to install the new
121+
version into your current installation directory.
122+
When upgrading from <productname>Postgres Pro</productname> 9.6.4.1 or
123+
lower, you must also use the <xref linkend="pgproupgrade"> script provided
124+
in this distribution. This script updates metadata information to
125+
handle catalog number format change introduced after
126+
<productname>Postgres Pro</productname> 9.6.4.1. If you are upgrading your
127+
<productname>Postgres Pro</productname> installation from a binary package, the
128+
<filename>pgpro_upgrade</filename> script is run automatically, unless you
129+
are prompted to run it manually.
130+
</para>
131+
<important>
132+
<para>
133+
If you run <literal>pgpro_upgrade</literal> manually,
134+
you must stop postgres service.
135+
The script must be run on behalf of the user owning the database
136+
(typically postgres). Running <literal>pgpro_upgrade</literal>
137+
as root will result in an error. For details, see <xref linkend="pgproupgrade">.
138+
</para>
139+
</important>
140+
<para>If you have compiled <productname>Postgres Pro</productname>
141+
from source code or created your database in a non-default location,
142+
you must run the <literal>pgpro_upgrade</literal> script manually.
143+
</para>
144+
<note>
145+
<para>On RPM-based Linux distributions, if you are upgrading from
146+
version 9.6.2.1 or lower, make sure to move the data directory from
147+
<filename>pgsql</filename> to the <filename>pgpro</filename>
148+
directory before running the <literal>pgpro_upgrade</literal> script.
149+
</para>
150+
</note>
151+
<para>To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore using
152+
<xref linkend="app-pg-dumpall">.
153+
</para>
154+
</sect2>
155+
</sect1>
3156
<sect1 id="release-pro-9-6-5-1">
4157
<title>Postgres Pro 9.6.5.1</title>
5158
<formalpara>
@@ -59,7 +212,7 @@
59212
a dump/restore is not required. Instead of the <literal>pg_upgrade</literal>,
60213
you must use the <literal>pgpro_upgrade</literal> script provided
61214
in this distribution. This script updates metadata information to
62-
handle catalog number format change introduced in
215+
handle catalog number format change introduced after
63216
<productname>Postgres Pro</productname> 9.6.4.1. If you are upgrading your
64217
<productname>Postgres Pro</productname> installation from a binary package, the
65218
<literal>pgpro_upgrade</literal> script is run automatically, or you

0 commit comments

Comments
 (0)