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

Commit 51ecf52

Browse files
tglsfdctglsfdc
committed
Update release notes for 9.1.4, 9.0.8, 8.4.12, 8.3.19.
1 parent a04dc87 commit 51ecf52

File tree

4 files changed

+1324
-0
lines changed

4 files changed

+1324
-0
lines changed

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

+229
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,235 @@
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-19">
5+
<title>Release 8.3.19</title>
6+
7+
<note>
8+
<title>Release Date</title>
9+
<simpara>2012-06-04</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a variety of fixes from 8.3.18.
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.19</title>
20+
21+
<para>
22+
A dump/restore is not required for those running 8.3.X.
23+
</para>
24+
25+
<para>
26+
However, if you are upgrading from a version earlier than 8.3.17,
27+
see the release notes for 8.3.17.
28+
</para>
29+
30+
</sect2>
31+
32+
<sect2>
33+
<title>Changes</title>
34+
35+
<itemizedlist>
36+
37+
<listitem>
38+
<para>
39+
Fix incorrect password transformation in
40+
<filename>contrib/pgcrypto</>'s DES <function>crypt()</> function
41+
(Solar Designer)
42+
</para>
43+
44+
<para>
45+
If a password string contained the byte value <literal>0x80</>, the
46+
remainder of the password was ignored, causing the password to be much
47+
weaker than it appeared. With this fix, the rest of the string is
48+
properly included in the DES hash. Any stored password values that are
49+
affected by this bug will thus no longer match, so the stored values may
50+
need to be updated. (CVE-2012-2143)
51+
</para>
52+
</listitem>
53+
54+
<listitem>
55+
<para>
56+
Ignore <literal>SECURITY DEFINER</> and <literal>SET</> attributes for
57+
a procedural language's call handler (Tom Lane)
58+
</para>
59+
60+
<para>
61+
Applying such attributes to a call handler could crash the server.
62+
(CVE-2012-2655)
63+
</para>
64+
</listitem>
65+
66+
<listitem>
67+
<para>
68+
Allow numeric timezone offsets in <type>timestamp</> input to be up to
69+
16 hours away from UTC (Tom Lane)
70+
</para>
71+
72+
<para>
73+
Some historical time zones have offsets larger than 15 hours, the
74+
previous limit. This could result in dumped data values being rejected
75+
during reload.
76+
</para>
77+
</listitem>
78+
79+
<listitem>
80+
<para>
81+
Fix timestamp conversion to cope when the given time is exactly the
82+
last DST transition time for the current timezone (Tom Lane)
83+
</para>
84+
85+
<para>
86+
This oversight has been there a long time, but was not noticed
87+
previously because most DST-using zones are presumed to have an
88+
indefinite sequence of future DST transitions.
89+
</para>
90+
</listitem>
91+
92+
<listitem>
93+
<para>
94+
Fix <type>text</> to <type>name</> and <type>char</> to <type>name</>
95+
casts to perform string truncation correctly in multibyte encodings
96+
(Karl Schnaitter)
97+
</para>
98+
</listitem>
99+
100+
<listitem>
101+
<para>
102+
Fix memory copying bug in <function>to_tsquery()</> (Heikki Linnakangas)
103+
</para>
104+
</listitem>
105+
106+
<listitem>
107+
<para>
108+
Fix slow session startup when <structname>pg_attribute</> is very large
109+
(Tom Lane)
110+
</para>
111+
112+
<para>
113+
If <structname>pg_attribute</> exceeds one-fourth of
114+
<varname>shared_buffers</>, cache rebuilding code that is sometimes
115+
needed during session start would trigger the synchronized-scan logic,
116+
causing it to take many times longer than normal. The problem was
117+
particularly acute if many new sessions were starting at once.
118+
</para>
119+
</listitem>
120+
121+
<listitem>
122+
<para>
123+
Ensure sequential scans check for query cancel reasonably often (Merlin
124+
Moncure)
125+
</para>
126+
127+
<para>
128+
A scan encountering many consecutive pages that contain no live tuples
129+
would not respond to interrupts meanwhile.
130+
</para>
131+
</listitem>
132+
133+
<listitem>
134+
<para>
135+
Ensure the Windows implementation of <function>PGSemaphoreLock()</>
136+
clears <varname>ImmediateInterruptOK</> before returning (Tom Lane)
137+
</para>
138+
139+
<para>
140+
This oversight meant that a query-cancel interrupt received later
141+
in the same query could be accepted at an unsafe time, with
142+
unpredictable but not good consequences.
143+
</para>
144+
</listitem>
145+
146+
<listitem>
147+
<para>
148+
Show whole-row variables safely when printing views or rules
149+
(Abbas Butt, Tom Lane)
150+
</para>
151+
152+
<para>
153+
Corner cases involving ambiguous names (that is, the name could be
154+
either a table or column name of the query) were printed in an
155+
ambiguous way, risking that the view or rule would be interpreted
156+
differently after dump and reload. Avoid the ambiguous case by
157+
attaching a no-op cast.
158+
</para>
159+
</listitem>
160+
161+
<listitem>
162+
<para>
163+
Ensure autovacuum worker processes perform stack depth checking
164+
properly (Heikki Linnakangas)
165+
</para>
166+
167+
<para>
168+
Previously, infinite recursion in a function invoked by
169+
auto-<command>ANALYZE</> could crash worker processes.
170+
</para>
171+
</listitem>
172+
173+
<listitem>
174+
<para>
175+
Fix logging collector to not lose log coherency under high load (Andrew
176+
Dunstan)
177+
</para>
178+
179+
<para>
180+
The collector previously could fail to reassemble large messages if it
181+
got too busy.
182+
</para>
183+
</listitem>
184+
185+
<listitem>
186+
<para>
187+
Fix logging collector to ensure it will restart file rotation
188+
after receiving <systemitem>SIGHUP</> (Tom Lane)
189+
</para>
190+
</listitem>
191+
192+
<listitem>
193+
<para>
194+
Fix PL/pgSQL's <command>GET DIAGNOSTICS</> command when the target
195+
is the function's first variable (Tom Lane)
196+
</para>
197+
</listitem>
198+
199+
<listitem>
200+
<para>
201+
Fix several performance problems in <application>pg_dump</> when
202+
the database contains many objects (Jeff Janes, Tom Lane)
203+
</para>
204+
205+
<para>
206+
<application>pg_dump</> could get very slow if the database contained
207+
many schemas, or if many objects are in dependency loops, or if there
208+
are many owned sequences.
209+
</para>
210+
</listitem>
211+
212+
<listitem>
213+
<para>
214+
Fix <filename>contrib/dblink</>'s <function>dblink_exec()</> to not leak
215+
temporary database connections upon error (Tom Lane)
216+
</para>
217+
</listitem>
218+
219+
<listitem>
220+
<para>
221+
Update time zone data files to <application>tzdata</> release 2012c
222+
for DST law changes in Antarctica, Armenia, Chile, Cuba, Falkland
223+
Islands, Gaza, Haiti, Hebron, Morocco, Syria, and Tokelau Islands;
224+
also historical corrections for Canada.
225+
</para>
226+
</listitem>
227+
228+
</itemizedlist>
229+
230+
</sect2>
231+
</sect1>
232+
4233
<sect1 id="release-8-3-18">
5234
<title>Release 8.3.18</title>
6235

0 commit comments

Comments
 (0)