1
1
<!-- doc/src/sgml/release-9.1.sgml -->
2
2
<!-- See header comment in release.sgml about typical markup -->
4
<sect1 id="release-9-1-5">
5
<title>Release 9.1.5</title>
8
<title>Release Date</title>
9
<simpara>2012-08-17</simpara>
13
This release contains a variety of fixes from 9.1.4.
14
For information about new features in the 9.1 major release, see
15
<xref linkend="release-9-1">.
19
<title>Migration to Version 9.1.5</title>
22
A dump/restore is not required for those running 9.1.X.
26
However, if you are upgrading from a version earlier than 9.1.4,
27
see the release notes for 9.1.4.
33
<title>Changes</title>
39
Prevent access to external files/URLs via XML entity references
40
(Noah Misch, Tom Lane)
44
<function>xml_parse()</> would attempt to fetch external files or
45
URLs as needed to resolve DTD and entity references in an XML value,
46
thus allowing unprivileged database users to attempt to fetch data
47
with the privileges of the database server. While the external data
48
wouldn't get returned directly to the user, portions of it could be
49
exposed in error messages if the data didn't parse as valid XML; and
50
in any case the mere ability to check existence of a file might be
51
useful to an attacker. (CVE-2012-3489)
57
Prevent access to external files/URLs via <filename>contrib/xml2</>'s
58
<function>xslt_process()</> (Peter Eisentraut)
62
<application>libxslt</> offers the ability to read and write both
63
files and URLs through stylesheet commands, thus allowing
64
unprivileged database users to both read and write data with the
65
privileges of the database server. Disable that through proper use
66
of <application>libxslt</>'s security options. (CVE-2012-3488)
70
Also, remove <function>xslt_process()</>'s ability to fetch documents
71
and stylesheets from external files/URLs. While this was a
72
documented <quote>feature</>, it was long regarded as a bad idea.
73
The fix for CVE-2012-3489 broke that capability, and rather than
74
expend effort on trying to fix it, we're just going to summarily
81
Prevent too-early recycling of btree index pages (Noah Misch)
85
When we allowed read-only transactions to skip assigning XIDs, we
86
introduced the possibility that a deleted btree page could be
87
recycled while a read-only transaction was still in flight to it.
88
This would result in incorrect index search results. The probability
89
of such an error occurring in the field seems very low because of the
90
timing requirements, but nonetheless it should be fixed.
96
Fix crash-safety bug with newly-created-or-reset sequences (Tom Lane)
100
If <command>ALTER SEQUENCE</> was executed on a freshly created or
101
reset sequence, and then precisely one <function>nextval()</> call
102
was made on it, and then the server crashed, WAL replay would restore
103
the sequence to a state in which it appeared that no
104
<function>nextval()</> had been done, thus allowing the first
105
sequence value to be returned again by the next
106
<function>nextval()</> call. In particular this could manifest for
107
<type>serial</> columns, since creation of a serial column's sequence
108
includes an <command>ALTER SEQUENCE OWNED BY</> step.
114
Fix race condition in <literal>enum</>-type value comparisons (Robert
119
Comparisons could fail when encountering an enum value added since
120
the current query started.
126
Fix <function>txid_current()</> to report the correct epoch when not
127
in hot standby (Heikki Linnakangas)
131
This fixes a regression introduced in the previous minor release.
137
Prevent selection of unsuitable replication connections as
138
the synchronous standby (Fujii Masao)
142
The master might improperly choose pseudo-servers such as
143
<application>pg_receivexlog</> or <application>pg_basebackup</>
144
as the synchronous standby, and then wait indefinitely for them.
150
Fix bug in startup of Hot Standby when a master transaction has many
151
subtransactions (Andres Freund)
155
This mistake led to failures reported as <quote>out-of-order XID
156
insertion in KnownAssignedXids</>.
162
Ensure the <filename>backup_label</> file is fsync'd after
163
<function>pg_start_backup()</> (Dave Kerr)
169
Fix timeout handling in walsender processes (Tom Lane)
173
WAL sender background processes neglected to establish a
174
<systemitem>SIGALRM</> handler, meaning they would wait forever in
175
some corner cases where a timeout ought to happen.
181
Wake walsenders after each background flush by walwriter (Andres
186
This greatly reduces replication delay when the workload contains
187
only asynchronously-committed transactions.
193
Fix <literal>LISTEN</>/<literal>NOTIFY</> to cope better with I/O
194
problems, such as out of disk space (Tom Lane)
198
After a write failure, all subsequent attempts to send more
199
<literal>NOTIFY</> messages would fail with messages like
200
<quote>Could not read from file "pg_notify/<replaceable>nnnn</>" at
201
offset <replaceable>nnnnn</>: Success</quote>.
207
Only allow autovacuum to be auto-canceled by a directly blocked
212
The original coding could allow inconsistent behavior in some cases;
213
in particular, an autovacuum could get canceled after less than
214
<literal>deadlock_timeout</> grace period.
220
Improve logging of autovacuum cancels (Robert Haas)
226
Fix log collector so that <literal>log_truncate_on_rotation</> works
227
during the very first log rotation after server start (Tom Lane)
233
Fix <literal>WITH</> attached to a nested set operation
234
(<literal>UNION</>/<literal>INTERSECT</>/<literal>EXCEPT</>)
241
Ensure that a whole-row reference to a subquery doesn't include any
242
extra <literal>GROUP BY</> or <literal>ORDER BY</> columns (Tom Lane)
248
Fix dependencies generated during <literal>ALTER TABLE ... ADD
249
CONSTRAINT USING INDEX</> (Tom Lane)
253
This command left behind a redundant <structname>pg_depend</> entry
254
for the index, which could confuse later operations, notably
255
<literal>ALTER TABLE ... ALTER COLUMN TYPE</> on one of the indexed
262
Fix <command>REASSIGN OWNED</> to work on extensions (Alvaro Herrera)
268
Disallow copying whole-row references in <literal>CHECK</>
269
constraints and index definitions during <command>CREATE TABLE</>
274
This situation can arise in <command>CREATE TABLE</> with
275
<literal>LIKE</> or <literal>INHERITS</>. The copied whole-row
276
variable was incorrectly labeled with the row type of the original
277
table not the new one. Rejecting the case seems reasonable for
278
<literal>LIKE</>, since the row types might well diverge later. For
279
<literal>INHERITS</> we should ideally allow it, with an implicit
280
coercion to the parent table's row type; but that will require more
281
work than seems safe to back-patch.
287
Fix memory leak in <literal>ARRAY(SELECT ...)</> subqueries (Heikki
288
Linnakangas, Tom Lane)
294
Fix planner to pass correct collation to operator selectivity
295
estimators (Tom Lane)
299
This was not previously required by any core selectivity estimation
300
function, but third-party code might need it.
306
Fix extraction of common prefixes from regular expressions (Tom Lane)
310
The code could get confused by quantified parenthesized
311
subexpressions, such as <literal>^(foo)?bar</>. This would lead to
312
incorrect index optimization of searches for such patterns.
318
Fix bugs with parsing signed
319
<replaceable>hh</><literal>:</><replaceable>mm</> and
320
<replaceable>hh</><literal>:</><replaceable>mm</><literal>:</><replaceable>ss</>
321
fields in <type>interval</> constants (Amit Kapila, Tom Lane)
327
Fix <application>pg_dump</> to better handle views containing partial
328
<literal>GROUP BY</> lists (Tom Lane)
332
A view that lists only a primary key column in <literal>GROUP BY</>,
333
but uses other table columns as if they were grouped, gets marked as
334
depending on the primary key. Improper handling of such primary key
335
dependencies in <application>pg_dump</> resulted in poorly-ordered
336
dumps, which at best would be inefficient to restore and at worst
337
could result in outright failure of a parallel
338
<application>pg_restore</> run.
344
In PL/Perl, avoid setting UTF8 flag when in SQL_ASCII encoding
345
(Alex Hunsaker, Kyotaro Horiguchi, Alvaro Herrera)
351
Use Postgres' encoding conversion functions, not Python's, when
352
converting a Python Unicode string to the server encoding in
353
PL/Python (Jan Urbanski)
357
This avoids some corner-case problems, notably that Python doesn't
358
support all the encodings Postgres does. A notable functional change
359
is that if the server encoding is SQL_ASCII, you will get the UTF-8
360
representation of the string; formerly, any non-ASCII characters in
361
the string would result in an error.
367
Fix mapping of PostgreSQL encodings to Python encodings in PL/Python
374
Report errors properly in <filename>contrib/xml2</>'s
375
<function>xslt_process()</> (Tom Lane)
381
Update time zone data files to <application>tzdata</> release 2012e
382
for DST law changes in Morocco and Tokelau
4
391
<sect1 id="release-9-1-4">
5
392
<title>Release 9.1.4</title>