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

Commit 29d4421

Browse files
tglsfdctglsfdc
committed
Update release notes for releases 9.0.3, 8.4.7, 8.3.14, and 8.2.20.
1 parent 1e4baa5 commit 29d4421

File tree

4 files changed

+520
-0
lines changed

4 files changed

+520
-0
lines changed

‎doc/src/sgml/release-8.2.sgml

+119
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,125 @@
11
<!-- doc/src/sgml/release-8.2.sgml -->
22
<!-- See header comment in release.sgml about typical markup -->
33

4+
<sect1 id="release-8-2-20">
5+
<title>Release 8.2.20</title>
6+
7+
<note>
8+
<title>Release date</title>
9+
<simpara>2011-01-31</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a variety of fixes from 8.2.19.
14+
For information about new features in the 8.2 major release, see
15+
<xref linkend="release-8-2">.
16+
</para>
17+
18+
<sect2>
19+
<title>Migration to Version 8.2.20</title>
20+
21+
<para>
22+
A dump/restore is not required for those running 8.2.X.
23+
However, if you are upgrading from a version earlier than 8.2.14,
24+
see the release notes for 8.2.14.
25+
</para>
26+
27+
</sect2>
28+
29+
<sect2>
30+
<title>Changes</title>
31+
32+
<itemizedlist>
33+
34+
<listitem>
35+
<para>
36+
Avoid failures when <command>EXPLAIN</> tries to display a simple-form
37+
<literal>CASE</> expression (Tom Lane)
38+
</para>
39+
40+
<para>
41+
If the <literal>CASE</>'s test expression was a constant, the planner
42+
could simplify the <literal>CASE</> into a form that confused the
43+
expression-display code, resulting in <quote>unexpected CASE WHEN
44+
clause</> errors.
45+
</para>
46+
</listitem>
47+
48+
<listitem>
49+
<para>
50+
Fix assignment to an array slice that is before the existing range
51+
of subscripts (Tom Lane)
52+
</para>
53+
54+
<para>
55+
If there was a gap between the newly added subscripts and the first
56+
pre-existing subscript, the code miscalculated how many entries needed
57+
to be copied from the old array's null bitmap, potentially leading to
58+
data corruption or crash.
59+
</para>
60+
</listitem>
61+
62+
<listitem>
63+
<para>
64+
Avoid unexpected conversion overflow in planner for very distant date
65+
values (Tom Lane)
66+
</para>
67+
68+
<para>
69+
The <type>date</> type supports a wider range of dates than can be
70+
represented by the <type>timestamp</> types, but the planner assumed it
71+
could always convert a date to timestamp with impunity.
72+
</para>
73+
</listitem>
74+
75+
<listitem>
76+
<para>
77+
Fix <application>pg_restore</>'s text output for large objects (BLOBs)
78+
when <varname>standard_conforming_strings</> is on (Tom Lane)
79+
</para>
80+
81+
<para>
82+
Although restoring directly to a database worked correctly, string
83+
escaping was incorrect if <application>pg_restore</> was asked for
84+
SQL text output and <varname>standard_conforming_strings</> had been
85+
enabled in the source database.
86+
</para>
87+
</listitem>
88+
89+
<listitem>
90+
<para>
91+
Fix erroneous parsing of <type>tsquery</> values containing
92+
<literal>... &amp; !(subexpression) | ...</literal> (Tom Lane)
93+
</para>
94+
95+
<para>
96+
Queries containing this combination of operators were not executed
97+
correctly. The same error existed in <filename>contrib/intarray</>'s
98+
<type>query_int</> type and <filename>contrib/ltree</>'s
99+
<type>ltxtquery</> type.
100+
</para>
101+
</listitem>
102+
103+
<listitem>
104+
<para>
105+
Fix bug in <filename>contrib/seg</>'s GiST picksplit algorithm
106+
(Alexander Korotkov)
107+
</para>
108+
109+
<para>
110+
This could result in considerable inefficiency, though not actually
111+
incorrect answers, in a GiST index on a <type>seg</> column.
112+
If you have such an index, consider <command>REINDEX</>ing it after
113+
installing this update. (This is identical to the bug that was fixed in
114+
<filename>contrib/cube</> in the previous update.)
115+
</para>
116+
</listitem>
117+
118+
</itemizedlist>
119+
120+
</sect2>
121+
</sect1>
122+
4123
<sect1 id="release-8-2-19">
5124
<title>Release 8.2.19</title>
6125

‎doc/src/sgml/release-8.3.sgml

+119
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,125 @@
11
<!-- doc/src/sgml/release-8.3.sgml -->
22
<!-- See header comment in release.sgml about typical markup -->
33

4+
<sect1 id="release-8-3-14">
5+
<title>Release 8.3.14</title>
6+
7+
<note>
8+
<title>Release date</title>
9+
<simpara>2011-01-31</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a variety of fixes from 8.3.13.
14+
For information about new features in the 8.3 major release, see
15+
<xref linkend="release-8-3">.
16+
</para>
17+
18+
<sect2>
19+
<title>Migration to Version 8.3.14</title>
20+
21+
<para>
22+
A dump/restore is not required for those running 8.3.X.
23+
However, if you are upgrading from a version earlier than 8.3.8,
24+
see the release notes for 8.3.8.
25+
</para>
26+
27+
</sect2>
28+
29+
<sect2>
30+
<title>Changes</title>
31+
32+
<itemizedlist>
33+
34+
<listitem>
35+
<para>
36+
Avoid failures when <command>EXPLAIN</> tries to display a simple-form
37+
<literal>CASE</> expression (Tom Lane)
38+
</para>
39+
40+
<para>
41+
If the <literal>CASE</>'s test expression was a constant, the planner
42+
could simplify the <literal>CASE</> into a form that confused the
43+
expression-display code, resulting in <quote>unexpected CASE WHEN
44+
clause</> errors.
45+
</para>
46+
</listitem>
47+
48+
<listitem>
49+
<para>
50+
Fix assignment to an array slice that is before the existing range
51+
of subscripts (Tom Lane)
52+
</para>
53+
54+
<para>
55+
If there was a gap between the newly added subscripts and the first
56+
pre-existing subscript, the code miscalculated how many entries needed
57+
to be copied from the old array's null bitmap, potentially leading to
58+
data corruption or crash.
59+
</para>
60+
</listitem>
61+
62+
<listitem>
63+
<para>
64+
Avoid unexpected conversion overflow in planner for very distant date
65+
values (Tom Lane)
66+
</para>
67+
68+
<para>
69+
The <type>date</> type supports a wider range of dates than can be
70+
represented by the <type>timestamp</> types, but the planner assumed it
71+
could always convert a date to timestamp with impunity.
72+
</para>
73+
</listitem>
74+
75+
<listitem>
76+
<para>
77+
Fix <application>pg_restore</>'s text output for large objects (BLOBs)
78+
when <varname>standard_conforming_strings</> is on (Tom Lane)
79+
</para>
80+
81+
<para>
82+
Although restoring directly to a database worked correctly, string
83+
escaping was incorrect if <application>pg_restore</> was asked for
84+
SQL text output and <varname>standard_conforming_strings</> had been
85+
enabled in the source database.
86+
</para>
87+
</listitem>
88+
89+
<listitem>
90+
<para>
91+
Fix erroneous parsing of <type>tsquery</> values containing
92+
<literal>... &amp; !(subexpression) | ...</literal> (Tom Lane)
93+
</para>
94+
95+
<para>
96+
Queries containing this combination of operators were not executed
97+
correctly. The same error existed in <filename>contrib/intarray</>'s
98+
<type>query_int</> type and <filename>contrib/ltree</>'s
99+
<type>ltxtquery</> type.
100+
</para>
101+
</listitem>
102+
103+
<listitem>
104+
<para>
105+
Fix bug in <filename>contrib/seg</>'s GiST picksplit algorithm
106+
(Alexander Korotkov)
107+
</para>
108+
109+
<para>
110+
This could result in considerable inefficiency, though not actually
111+
incorrect answers, in a GiST index on a <type>seg</> column.
112+
If you have such an index, consider <command>REINDEX</>ing it after
113+
installing this update. (This is identical to the bug that was fixed in
114+
<filename>contrib/cube</> in the previous update.)
115+
</para>
116+
</listitem>
117+
118+
</itemizedlist>
119+
120+
</sect2>
121+
</sect1>
122+
4123
<sect1 id="release-8-3-13">
5124
<title>Release 8.3.13</title>
6125

‎doc/src/sgml/release-8.4.sgml

+119
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,125 @@
11
<!-- doc/src/sgml/release-8.4.sgml -->
22
<!-- See header comment in release.sgml about typical markup -->
33

4+
<sect1 id="release-8-4-7">
5+
<title>Release 8.4.7</title>
6+
7+
<note>
8+
<title>Release date</title>
9+
<simpara>2011-01-31</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a variety of fixes from 8.4.6.
14+
For information about new features in the 8.4 major release, see
15+
<xref linkend="release-8-4">.
16+
</para>
17+
18+
<sect2>
19+
<title>Migration to Version 8.4.7</title>
20+
21+
<para>
22+
A dump/restore is not required for those running 8.4.X.
23+
However, if you are upgrading from a version earlier than 8.4.2,
24+
see the release notes for 8.4.2.
25+
</para>
26+
27+
</sect2>
28+
29+
<sect2>
30+
<title>Changes</title>
31+
32+
<itemizedlist>
33+
34+
<listitem>
35+
<para>
36+
Avoid failures when <command>EXPLAIN</> tries to display a simple-form
37+
<literal>CASE</> expression (Tom Lane)
38+
</para>
39+
40+
<para>
41+
If the <literal>CASE</>'s test expression was a constant, the planner
42+
could simplify the <literal>CASE</> into a form that confused the
43+
expression-display code, resulting in <quote>unexpected CASE WHEN
44+
clause</> errors.
45+
</para>
46+
</listitem>
47+
48+
<listitem>
49+
<para>
50+
Fix assignment to an array slice that is before the existing range
51+
of subscripts (Tom Lane)
52+
</para>
53+
54+
<para>
55+
If there was a gap between the newly added subscripts and the first
56+
pre-existing subscript, the code miscalculated how many entries needed
57+
to be copied from the old array's null bitmap, potentially leading to
58+
data corruption or crash.
59+
</para>
60+
</listitem>
61+
62+
<listitem>
63+
<para>
64+
Avoid unexpected conversion overflow in planner for very distant date
65+
values (Tom Lane)
66+
</para>
67+
68+
<para>
69+
The <type>date</> type supports a wider range of dates than can be
70+
represented by the <type>timestamp</> types, but the planner assumed it
71+
could always convert a date to timestamp with impunity.
72+
</para>
73+
</listitem>
74+
75+
<listitem>
76+
<para>
77+
Fix <application>pg_restore</>'s text output for large objects (BLOBs)
78+
when <varname>standard_conforming_strings</> is on (Tom Lane)
79+
</para>
80+
81+
<para>
82+
Although restoring directly to a database worked correctly, string
83+
escaping was incorrect if <application>pg_restore</> was asked for
84+
SQL text output and <varname>standard_conforming_strings</> had been
85+
enabled in the source database.
86+
</para>
87+
</listitem>
88+
89+
<listitem>
90+
<para>
91+
Fix erroneous parsing of <type>tsquery</> values containing
92+
<literal>... &amp; !(subexpression) | ...</literal> (Tom Lane)
93+
</para>
94+
95+
<para>
96+
Queries containing this combination of operators were not executed
97+
correctly. The same error existed in <filename>contrib/intarray</>'s
98+
<type>query_int</> type and <filename>contrib/ltree</>'s
99+
<type>ltxtquery</> type.
100+
</para>
101+
</listitem>
102+
103+
<listitem>
104+
<para>
105+
Fix bug in <filename>contrib/seg</>'s GiST picksplit algorithm
106+
(Alexander Korotkov)
107+
</para>
108+
109+
<para>
110+
This could result in considerable inefficiency, though not actually
111+
incorrect answers, in a GiST index on a <type>seg</> column.
112+
If you have such an index, consider <command>REINDEX</>ing it after
113+
installing this update. (This is identical to the bug that was fixed in
114+
<filename>contrib/cube</> in the previous update.)
115+
</para>
116+
</listitem>
117+
118+
</itemizedlist>
119+
120+
</sect2>
121+
</sect1>
122+
4123
<sect1 id="release-8-4-6">
5124
<title>Release 8.4.6</title>
6125

0 commit comments

Comments
 (0)