<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.1. Release 11.5</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><link rel="prev" href="release.html" title="Appendix E. Release Notes" /><link rel="next" href="release-11-4.html" title="E.2. Release 11.4" /></head><body><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">E.1. Release 11.5</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="release.html" title="Appendix E. Release Notes">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="release.html" title="Appendix E. Release Notes">Up</a></td><th width="60%" align="center">Appendix E. Release Notes</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 11.5 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="release-11-4.html" title="E.2. Release 11.4">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="RELEASE-11-5"><div class="titlepage"><div><div><h2 class="title" style="clear: both">E.1. Release 11.5</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="sect2"><a href="release-11-5.html#id-1.11.6.5.4">E.1.1. Migration to Version 11.5</a></span></dt><dt><span class="sect2"><a href="release-11-5.html#id-1.11.6.5.5">E.1.2. Changes</a></span></dt></dl></div><p><strong>Release date: </strong>2019-08-08</p><p>
This release contains a variety of fixes from 11.4.
For information about new features in major release 11, see
<a class="xref" href="release-11.html" title="E.6. Release 11">Section E.6</a>.
</p><div class="sect2" id="id-1.11.6.5.4"><div class="titlepage"><div><div><h3 class="title">E.1.1. Migration to Version 11.5</h3></div></div></div><p>
A dump/restore is not required for those running 11.X.
</p><p>
However, if you are upgrading from a version earlier than 11.1,
see <a class="xref" href="release-11-1.html" title="E.5. Release 11.1">Section E.5</a>.
</p></div><div class="sect2" id="id-1.11.6.5.5"><div class="titlepage"><div><div><h3 class="title">E.1.2. Changes</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Require schema qualification to cast to a temporary type when using
functional cast syntax (Noah Misch)
</p><p>
We have long required invocations of temporary functions to
explicitly specify the temporary schema, that
is <code class="literal">pg_temp.<em class="replaceable"><code>func_name</code></em>(<em class="replaceable"><code>args</code></em>)</code>.
Require this as well for casting to temporary types using functional
notation, for
example <code class="literal">pg_temp.<em class="replaceable"><code>type_name</code></em>(<em class="replaceable"><code>arg</code></em>)</code>.
Otherwise it's possible to capture a function call using a temporary
object, allowing privilege escalation in much the same ways that we
blocked in CVE-2007-2138.
(CVE-2019-10208)
</p></li><li class="listitem"><p>
Fix execution of hashed subplans that require cross-type comparison
(Tom Lane, Andreas Seltenreich)
</p><p>
Hashed subplans used the outer query's original comparison operator
to compare entries of the hash table. This is the wrong thing if
that operator is cross-type, since all the hash table entries will
be of the subquery's output type. For the set of hashable
cross-type operators in core <span class="productname">PostgreSQL</span>,
this mistake seems nearly harmless on 64-bit machines, but it can
result in crashes or perhaps unauthorized disclosure of server
memory on 32-bit machines. Extensions might provide hashable
cross-type operators that create larger risks.
(CVE-2019-10209)
</p></li><li class="listitem"><p>
Fix failure of <code class="command">ALTER TABLE ... ALTER COLUMN TYPE</code>
when altering multiple columns' types in one command (Tom Lane)
</p><p>
This fixes a regression introduced in the most recent minor releases:
indexes using the altered columns were not processed correctly,
leading to strange failures during <code class="command">ALTER TABLE</code>.
</p></li><li class="listitem"><p>
Prevent dropping a partitioned table's trigger if there are pending
trigger events in child partitions (Álvaro Herrera)
</p><p>
This notably applies to foreign key constraints, since those are
implemented by triggers.
</p></li><li class="listitem"><p>
Include user-specified trigger arguments when copying a trigger
definition from a partitioned table to one of its partitions
(Patrick McHardy)
</p></li><li class="listitem"><p>
Install dependencies to prevent dropping partition key columns
(Tom Lane)
</p><p>
<code class="command">ALTER TABLE ... DROP COLUMN</code> will refuse to drop
a column that is a partition key column. However, indirect drops
(such as a cascade from dropping a key column's data type) had no
such check, allowing the deletion of a key column. This resulted in
a badly broken partitioned table that could neither be accessed nor
dropped.
</p><p>
This fix adds <code class="structname">pg_depend</code> entries that
enforce that the whole partitioned table, not just the key column,
will be dropped if a cascaded drop forces removal of the key column.
However, such entries will only be created when a partitioned table
is created; so this fix does not remove the risk for pre-existing
partitioned tables. The issue can only arise for partition key
columns of non-built-in data types, so it seems not to be a hazard
for most users.
</p></li><li class="listitem"><p>
Ensure that column numbers are correctly mapped between a partitioned
table and its default partition (Amit Langote)
</p><p>
Some operations misbehaved if the mapping wasn't exactly one-to-one,
for example if there were dropped columns in one table and not the
other.
</p></li><li class="listitem"><p>
Ignore partitions that are foreign tables when creating indexes on
partitioned tables (Álvaro Herrera)
</p><p>
Previously an error was thrown on encountering a foreign-table
partition, but that's unhelpful and doesn't protect against any
actual problem.
</p></li><li class="listitem"><p>
Prune a partitioned table's default partition (that is, avoid
uselessly scanning it) in more cases (Yuzuko Hosoya)
</p></li><li class="listitem"><p>
Fix possible failure to prune partitions when there are
multiple partition key columns of <code class="type">boolean</code> type
(David Rowley)
</p></li><li class="listitem"><p>
Don't optimize away <code class="literal">GROUP BY</code> columns when the
table involved is an inheritance parent (David Rowley)
</p><p>
Normally, if a table's primary key column(s) are included
in <code class="literal">GROUP BY</code>, it's safe to drop any other grouping
columns, since the primary key columns are enough to make the groups
unique. This rule does not work if the query is also reading
inheritance child tables, though; the parent's uniqueness does not
extend to the children.
</p></li><li class="listitem"><p>
Avoid incorrect use of parallel hash join for semi-join queries
(Thomas Munro)
</p><p>
This error resulted in duplicate result rows from
some <code class="literal">EXISTS</code> queries.
</p></li><li class="listitem"><p>
Avoid using unnecessary sort steps for some queries
with <code class="literal">GROUPING SETS</code> (Andrew Gierth, Richard Guo)
</p></li><li class="listitem"><p>
Fix possible failure of planner's index endpoint probes (Tom Lane)
</p><p>
When using a recently-created index to determine the minimum or
maximum value of a column, the planner could select a recently-dead
tuple that does not actually contain the endpoint value. In the
worst case the tuple might contain a null, resulting in a visible
error <span class="quote">“<span class="quote">found unexpected null value in index</span>”</span>; more
likely we would just end up using the wrong value, degrading the
quality of planning estimates.
</p></li><li class="listitem"><p>
Fix failure to access trigger transition tables
during <code class="literal">EvalPlanQual</code> rechecks (Alex Aktsipetrov)
</p><p>
Triggers that rely on transition tables sometimes failed in the
presence of concurrent updates.
</p></li><li class="listitem"><p>
Fix mishandling of multi-column foreign keys when rebuilding a
foreign key constraint (Tom Lane)
</p><p>
<code class="command">ALTER TABLE</code> could make an incorrect decision about
whether revalidation of a foreign key is necessary, if not all
columns of the key are of the same type. It seems likely that the
error would always have been in the conservative direction, that is
revalidating unnecessarily.
</p></li><li class="listitem"><p>
Don't build extended statistics for inheritance trees (Tomas Vondra)
</p><p>
This avoids a <span class="quote">“<span class="quote">tuple already updated by self</span>”</span> error
during <code class="command">ANALYZE</code>.
</p></li><li class="listitem"><p>
Avoid spurious deadlock errors when upgrading a tuple lock
(Oleksii Kliukin)
</p><p>
When two or more transactions are waiting for a transaction T1 to
release a tuple-level lock, and T1 upgrades its lock to a higher
level, a spurious deadlock among the waiting transactions could be
reported when T1 finishes.
</p></li><li class="listitem"><p>
Fix failure to resolve deadlocks involving multiple parallel worker
processes (Rui Hai Jiang)
</p><p>
It is not clear whether this bug is reachable with non-artificial
queries, but if it did happen, the queries involved in an
otherwise-resolvable deadlock would block until canceled.
</p></li><li class="listitem"><p>
Prevent incorrect canonicalization of date ranges
with <code class="literal">infinity</code> endpoints (Laurenz Albe)
</p><p>
It's incorrect to try to convert an open range to a closed one or
vice versa by incrementing or decrementing the endpoint value, if
the endpoint is infinite; so leave the range alone in such cases.
</p></li><li class="listitem"><p>
Fix loss of fractional digits when converting very
large <code class="type">money</code> values to <code class="type">numeric</code> (Tom Lane)
</p></li><li class="listitem"><p>
Fix printing of <code class="literal">BTREE_META_CLEANUP</code> WAL records
(Michael Paquier)
</p></li><li class="listitem"><p>
Prevent assertion failures due to mishandling of version-2 btree
metapages (Peter Geoghegan)
</p></li><li class="listitem"><p>
Fix spinlock assembly code for MIPS CPUs so that it works on
MIPS r6 (YunQiang Su)
</p></li><li class="listitem"><p>
Ensure that a record or row value returned from a PL/pgSQL function
is marked with the function's declared composite type (Tom Lane)
</p><p>
This avoids problems if the result is stored directly into a table.
</p></li><li class="listitem"><p>
Make <span class="application">libpq</span> ignore carriage return
(<code class="literal">\r</code>) in connection service files
(Tom Lane, Michael Paquier)
</p><p>
In some corner cases, service files containing Windows-style
newlines could be mis-parsed, resulting in connection failures.
</p></li><li class="listitem"><p>
In <span class="application">psql</span>, avoid offering incorrect tab
completion options
after <code class="literal">SET <em class="replaceable"><code>variable</code></em> =</code>
(Tom Lane)
</p></li><li class="listitem"><p>
Fix a small memory leak in <span class="application">psql</span>'s
<code class="literal">\d</code> command (Tom Lane)
</p></li><li class="listitem"><p>
Fix <span class="application">pg_dump</span> to ensure that custom operator
classes are dumped in the right order (Tom Lane)
</p><p>
If a user-defined opclass is the subtype opclass of a user-defined
range type, related objects were dumped in the wrong order,
producing an unrestorable dump. (The underlying failure to handle
opclass dependencies might manifest in other cases too, but this is
the only known case.)
</p></li><li class="listitem"><p>
Fix possible lockup in <span class="application">pgbench</span> when
using <code class="option">-R</code> option (Fabien Coelho)
</p></li><li class="listitem"><p>
Improve reliability of <code class="filename">contrib/amcheck</code>'s index
verification (Peter Geoghegan)
</p></li><li class="listitem"><p>
Fix handling of Perl <code class="literal">undef</code> values
in <code class="filename">contrib/jsonb_plperl</code> (Ivan Panchenko)
</p></li><li class="listitem"><p>
Fix <code class="filename">contrib/passwordcheck</code> to coexist with other
users of <code class="varname">check_password_hook</code> (Michael Paquier)
</p></li><li class="listitem"><p>
Fix <code class="filename">contrib/sepgsql</code> tests to work under recent
SELinux releases (Mike Palmiotto)
</p></li><li class="listitem"><p>
Improve stability of <code class="filename">src/test/kerberos</code>
and <code class="filename">src/test/ldap</code> regression tests
(Thomas Munro, Tom Lane)
</p></li><li class="listitem"><p>
Improve stability of <code class="filename">src/test/recovery</code>
regression tests (Michael Paquier)
</p></li><li class="listitem"><p>
Reduce <span class="systemitem">stderr</span> output
from <span class="application">pg_upgrade</span>'s test script (Tom Lane)
</p></li><li class="listitem"><p>
Fix <span class="application">pgbench</span> regression tests to work on
Windows (Fabien Coelho)
</p></li><li class="listitem"><p>
Fix TAP tests to work with msys Perl, in cases where the build
directory is on a non-root msys mount point (Noah Misch)
</p></li><li class="listitem"><p>
Support building Postgres with Microsoft Visual Studio 2019
(Haribabu Kommi)
</p></li><li class="listitem"><p>
In Visual Studio builds, honor <code class="literal">WindowsSDKVersion</code>
environment variable, if that's set (Peifeng Qiu)
</p><p>
This fixes build failures in some configurations.
</p></li><li class="listitem"><p>
Support OpenSSL 1.1.0 and newer in Visual Studio builds
(Juan José Santamaría Flecha, Michael Paquier)
</p></li><li class="listitem"><p>
Allow <span class="application">make</span> options to be passed down
to <span class="application">gmake</span> when non-GNU make is invoked at
the top level (Thomas Munro)
</p></li><li class="listitem"><p>
Avoid choosing <code class="literal">localtime</code>
or <code class="literal">posixrules</code> as <code class="varname">TimeZone</code>
during <span class="application">initdb</span> (Tom Lane)
</p><p>
In some cases <span class="application">initdb</span> would choose one of
these artificial zone names over the <span class="quote">“<span class="quote">real</span>”</span> zone name.
Prefer any other match to the C library's timezone behavior over
these two.
</p></li><li class="listitem"><p>
Adjust <code class="structname">pg_timezone_names</code> view to show
the <code class="literal">Factory</code> time zone if and only if it has a
short abbreviation (Tom Lane)
</p><p>
Historically, IANA set up this artificial zone with
an <span class="quote">“<span class="quote">abbreviation</span>”</span> like <code class="literal">Local time zone must be
set--see zic manual page</code>. Modern versions of the tzdb
database show <code class="literal">-00</code> instead, but some platforms
alter the data to show one or another of the historical phrases.
Show this zone only if it uses the modern abbreviation.
</p></li><li class="listitem"><p>
Sync our copy of the timezone library with IANA tzcode release 2019b
(Tom Lane)
</p><p>
This adds support for <span class="application">zic</span>'s new <code class="option">-b
slim</code> option to reduce the size of the installed zone files.
We are not currently using that, but may enable it in future.
</p></li><li class="listitem"><p>
Update time zone data files to <span class="application">tzdata</span>
release 2019b for DST law changes in Brazil, plus
historical corrections for Hong Kong, Italy, and Palestine.
</p></li></ul></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="release.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="release.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="release-11-4.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix E. Release Notes </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> E.2. Release 11.4</td></tr></table></div></body></html>
