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

Commit aff8118

Browse files
vbwagnervbwagner
committed
Merge branch 'PGPRO10' into PGPROEE10
2 parents 40d9345 + 23b1e33 commit aff8118

File tree

3 files changed

+154
-47
lines changed

3 files changed

+154
-47
lines changed

‎contrib/mchar/Makefile

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,10 @@ OBJS = mchar_io.o mchar_proc.o mchar_op.o mchar_recode.o \
44
EXTENSION = mchar
55
DATA = mchar--1.0.sql
66
DOCS = README.mchar
7-
REGRESS = init mchar mvarchar mm like compat
7+
REGRESS = init mchar mvarchar like
8+
ifndef NO_LOCALE
9+
REGRESS += mm compat
10+
endif
811
PGFIELDDESC = "mchar - mchar type implementation"
912

1013
ifdef USE_PGXS

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

Lines changed: 50 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,9 @@
99
<sect2>
1010
<title>Overview</title>
1111
<para>This release is based on <productname>PostgreSQL</productname> 10.3
12-
and includes all the new features introduced in PostgreSQL 10, as well as
13-
bug fixes implemented in PostgreSQL 10.3. For their detailed description,
14-
see <link linkend="release-10">PostgreSQL 10 Release Notes</link> and
15-
<link linkend="release-10-3">PostgreSQL 10.3 Release Notes</link>, respectively.
12+
and <productname>Postgres Pro Standard</productname> 10.3.1. All
13+
changes inherited from <productname>PostgreSQL</productname> 10.3 are listed in
14+
<link linkend="release-10-3"><productname>PostgreSQL</productname> 10.3 Release Notes</link>.
1615
Other major changes and enhancements are as follows:</para>
1716
<itemizedlist spacing="compact">
1817
<listitem>
@@ -23,53 +22,65 @@
2322
</listitem>
2423
<listitem>
2524
<para>
26-
Fixed search for mchar and mvarchar types via search_path to make
27-
these types dumpable even with cleaned up search path.
25+
Fixed search for <type>mchar</type> and <type>mvarchar</type> types via
26+
<varname>search_path</varname>. These types can now be dumped even with
27+
the cleaned up search path.
2828
</para>
2929
<!-- 355211667eaf7469696b3316ef7b935c6cc9e78c -->
3030
</listitem>
3131
<listitem>
3232
<para>
33-
Added <literal>--add-collprovider</literal> option to <command>pg_dump</command> utility.
33+
Added <literal>--add-collprovider</literal> option to
34+
<command>pg_dump</command> and <command>pg_dumpall</command> utilities.
3435
</para>
3536
<!-- 431100a1cd03808b0dc1cdfdd065398ec08b59e1 -->
3637
</listitem>
3738
<listitem>
3839
<para>Updated the <link linkend="app-pgprobackup"><application>pg_probackup</application></link>
39-
utility from 2.0.14 to 2.0.16 version.</para>
40+
utility from version 2.0.14 to 2.0.16, which includes the following new features:</para>
4041
<itemizedlist>
4142
<listitem>
42-
<para>Infinite loop while page validation has been fixed.</para>
43-
</listitem>
44-
<listitem>
45-
<para>Fixed segfault for the case of parallel ptrack connections.</para>
46-
</listitem>
47-
<listitem>
48-
<para>Allowed to use <literal>delete-wal</literal> option wihtout <literal>delete-expired</literal>.</para>
49-
</listitem>
50-
<listitem>
51-
<para>Allowed to use <literal>pg_ptrack_get_block</literal> if it is available and page is invalid.</para>
52-
</listitem>
53-
<listitem>
54-
<para>Fixed CVE-2018-1058. Schema name explicitly used on the every function call.</para>
55-
</listitem>
56-
<listitem>
57-
<para>Handle datafiles in directory <literal>global</literal> as datafiles.</para>
58-
</listitem>
59-
<listitem>
60-
<para>Do not copy ptrack files from directory <literal>global</literal> to backup anymore.</para>
61-
</listitem>
62-
<listitem>
63-
<para>
64-
Check if <literal>--instance</literal> is specified for <command>VALIDATE</command> with target parameters.
65-
</para>
66-
</listitem>
67-
</itemizedlist>
43+
<para>Fixed an infinite loop that could happen during page validation.</para>
44+
</listitem>
45+
<listitem>
46+
<para>Fixed segfault for the case of parallel <literal>PTRACK</literal> connections.</para>
47+
</listitem>
48+
<listitem>
49+
<para>Allowed to use the <literal>delete-wal</literal> option without <literal>delete-expired</literal>.</para>
50+
</listitem>
51+
<listitem>
52+
<para>
53+
Schema name is now explicitly used in all function calls
54+
to address CVE-2018-1058 security issue.
55+
</para>
56+
</listitem>
57+
<listitem>
58+
<para>
59+
Data files in the <filename>global</filename> directory
60+
are now handled properly: <application>pg_probackup</application>
61+
can now perform incremental backups and run checksum validation
62+
for such data files.
63+
</para>
64+
</listitem>
65+
<listitem>
66+
<para>
67+
<literal>PTRACK</literal> files from the <filename>global</filename>
68+
directory are not copied to backups anymore.
69+
</para>
70+
</listitem>
71+
<listitem>
72+
<para>
73+
<application>pg_probackup</application> now checks that the
74+
<literal>--instance</literal> option is specified for the
75+
<literal>VALIDATE</literal> command.
76+
</para>
77+
</listitem>
78+
</itemizedlist>
6879
<!-- 76afcee1255d94ebc84f89ba336827999436a4c2 -->
6980
</listitem>
7081
<listitem>
71-
<para>Fixed problem with sort order of some russian letters in the
72-
mchar module.
82+
<para>Fixed an issue with sort ordering of some Russian letters in the
83+
<filename>mchar</filename> module.
7384
Use <command>REINDEX DATABASE</command> command to update indexes.</para>
7485
<!-- 06113a6d9d0fc9b88346c69011158b589ca487e7 -->
7586
</listitem>
@@ -85,7 +96,9 @@
8596
<para>To migrate from <productname>PostgreSQL</productname> or
8697
<productname>Postgres Pro Standard</productname> versions based on
8798
any previous <productname>PostgreSQL</productname> major release, see the instructions
88-
in <link linkend="release-pro-10-3-1">Postgres Pro Standard 10.3.1 Release Notes</link>.
99+
in <link linkend="release-pro-10-1-1">Postgres Pro Standard 10.1.1 Release Notes</link>.
100+
If you are opting for a dump/restore, make sure to use the <literal>--add-collprovider</literal>
101+
option to correctly choose the collation provider for the migrated database.
89102
</para>
90103

91104
</sect2>

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

Lines changed: 100 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,122 @@
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-8-1">
4-
<title>Postgres Pro Standard 9.6.8.1</title>
3+
<sect1 id="release-pro-9-6-8-2">
4+
<title>Postgres Pro Standard 9.6.8.2</title>
55
<formalpara>
66
<title>Release date:</title>
7-
<para>2018-03-01</para>
7+
<para>2018-03-20</para>
88
</formalpara>
99
<sect2>
1010
<title>Overview</title>
1111
<para>This release is based on <productname>PostgreSQL</productname> 9.6.8
12-
and <productname>Postgres Pro Standard</productname> 9.6.7.1. All improvements
12+
and <productname>Postgres Pro Standard</productname> 9.6.8.1. All improvements
1313
inherited from <productname>PostgreSQL</productname> 9.6.8 are listed
1414
in <link linkend="release-9-6-8"><productname>PostgreSQL</productname> 9.6.8 Release Notes</link>.</para>
1515
<para>Major enhancements over <productname>Postgres Pro Standard</productname>
16-
9.6.7.1 include:</para>
16+
9.6.8.1 include:</para>
1717
<itemizedlist>
18+
19+
<listitem>
20+
<para>Updated
21+
the <link linkend="app-pgprobackup"><application>pg_probackup</application></link>
22+
utility from version 2.0.11 to 2.0.16, which includes the following new features:</para>
23+
<itemizedlist>
24+
<listitem>
25+
<para>Fixed an infinite loop that could happen during page validation.</para>
26+
</listitem>
27+
<listitem>
28+
<para>Fixed segfault for the case of parallel <literal>PTRACK</literal> connections.</para>
29+
</listitem>
30+
<listitem>
31+
<para>Allowed to use the <literal>delete-wal</literal> option without <literal>delete-expired</literal>.</para>
32+
</listitem>
33+
<listitem>
34+
<para>Fixed CVE-2018-1058. Schema name is now explicitly used on every function call.</para>
35+
</listitem>
36+
</itemizedlist>
37+
<!--
38+
76afcee1255d94ebc84f89ba336827999436a4c2
39+
-->
40+
</listitem>
1841
<listitem>
1942
<para>
20-
The <function>pgpro_build</function> function has been renamed
21-
to <function>pgpro_source_id</function>.
43+
You can now use <function>pgpro_build</function> function
44+
to get the latest commit ID for the source files of the current release.
2245
</para>
23-
<!--
24-
4328669d24cf070a12b585d1bcbfb0fc06c1b707
46+
<!--
47+
f26daaf0d3257d4bc8ed8b59d7e560d37a61117e
2548
-->
2649
</listitem>
50+
<listitem>
51+
<para>Fixed an issue with sort ordering of some Russian letters in the
52+
<filename>mchar</filename> module.
53+
Use <command>REINDEX DATABASE</command> command to update indexes.</para>
54+
<!-- e3b18fa73987222f1847ecc01cf792dc34bd37a5 -->
55+
</listitem>
2756
</itemizedlist>
2857
</sect2>
58+
<sect2>
59+
<title>Migration to Version 9.6.8.2</title>
60+
<para>Depending on your current installation, the upgrade procedure will differ.
61+
</para>
62+
<para>To upgrade from a <productname>Postgres Pro Standard</productname> version based on
63+
any previous <productname>PostgreSQL</productname> major release, you can perform a dump/restore using
64+
<xref linkend="app-pg-dumpall">, or use the <xref linkend="pgupgrade"> utility.
65+
The first option is safer, while the second is faster and can significantly
66+
speed up the upgrade process for large databases.
67+
</para>
68+
<para>To upgrade from a <productname>Postgres Pro Standard</productname> version
69+
based on the same <productname>PostgreSQL</productname> major release,
70+
a dump/restore is not required. If you are upgrading from
71+
<productname>Postgres Pro Standard</productname> 9.6.7.1 or
72+
lower, you must also use the <filename>pgpro_upgrade</filename> script provided
73+
in this distribution. This script updates metadata information to handle
74+
catalog number format change introduced after
75+
<productname>Postgres Pro Standard</productname> 9.6.4.1, as well as
76+
rename the <function>pgpro_build</function> function to <function>pgpro_source_id</function>.
77+
If you are upgrading your
78+
<productname>Postgres Pro</productname> installation from a binary package, the
79+
<filename>pgpro_upgrade</filename> script is run automatically, unless you
80+
are prompted to run it manually.
81+
</para>
82+
<important>
83+
<para>
84+
If you run <literal>pgpro_upgrade</literal> manually,
85+
you must stop postgres service.
86+
The script must be run on behalf of the user owning the database
87+
(typically postgres). Running <literal>pgpro_upgrade</literal>
88+
as root will result in an error.
89+
</para>
90+
</important>
91+
<para>If you have compiled <productname>Postgres Pro</productname>
92+
from source code or created your database in a non-default location,
93+
you must run the <literal>pgpro_upgrade</literal> script manually.
94+
</para>
95+
<note>
96+
<para>On RPM-based Linux distributions, if you are upgrading from
97+
version 9.6.2.1 or lower, make sure to move the data directory from
98+
<filename>pgsql</filename> to the <filename>pgpro</filename>
99+
directory before running the <literal>pgpro_upgrade</literal> script.
100+
</para>
101+
</note>
102+
<para>To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore using
103+
<xref linkend="app-pg-dumpall">.
104+
</para>
105+
</sect2>
106+
</sect1>
107+
<sect1 id="release-pro-9-6-8-1">
108+
<title>Postgres Pro Standard 9.6.8.1</title>
109+
<formalpara>
110+
<title>Release date:</title>
111+
<para>2018-03-01</para>
112+
</formalpara>
113+
<sect2>
114+
<title>Overview</title>
115+
<para>This release is based on <productname>PostgreSQL</productname> 9.6.8
116+
and <productname>Postgres Pro Standard</productname> 9.6.7.1. All improvements
117+
inherited from <productname>PostgreSQL</productname> 9.6.8 are listed
118+
in <link linkend="release-9-6-8"><productname>PostgreSQL</productname> 9.6.8 Release Notes</link>.</para>
119+
</sect2>
29120
<sect2>
30121
<title>Migration to Version 9.6.8.1</title>
31122
<para>Depending on your current installation, the upgrade procedure will differ.

0 commit comments

Comments
 (0)