| Server IP : 104.21.25.180 / Your IP : 162.159.115.42 Web Server : Apache/2.4.37 System : Linux almalinux.duckdns.org 4.18.0-553.111.1.el8_10.x86_64 #1 SMP Sun Mar 8 20:06:07 EDT 2026 x86_64 User : ricodeal ( 1046) PHP Version : 7.4.33 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/postgresql-docs/html/ |
Upload File : |
<?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.21. Release 10.3</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="[email protected]" /><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><link rel="prev" href="release-10-4.html" title="E.20. Release 10.4" /><link rel="next" href="release-10-2.html" title="E.22. Release 10.2" /></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.21. Release 10.3</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="release-10-4.html" title="E.20. Release 10.4">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 10.23 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="release-10-2.html" title="E.22. Release 10.2">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="RELEASE-10-3"><div class="titlepage"><div><div><h2 class="title" style="clear: both">E.21. Release 10.3</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="sect2"><a href="release-10-3.html#id-1.11.6.25.4">E.21.1. Migration to Version 10.3</a></span></dt><dt><span class="sect2"><a href="release-10-3.html#id-1.11.6.25.5">E.21.2. Changes</a></span></dt></dl></div><p><strong>Release date: </strong>2018-03-01</p><p> This release contains a variety of fixes from 10.2.
For information about new features in major release 10, see
<a class="xref" href="release-10.html" title="E.24. Release 10">Section E.24</a>.
</p><div class="sect2" id="id-1.11.6.25.4"><div class="titlepage"><div><div><h3 class="title">E.21.1. Migration to Version 10.3</h3></div></div></div><p> A dump/restore is not required for those running 10.X.
</p><p> However, if you run an installation in which not all users are mutually
trusting, or if you maintain an application or extension that is
intended for use in arbitrary situations, it is strongly recommended
that you read the documentation changes described in the first changelog
entry below, and take suitable steps to ensure that your installation or
code is secure.
</p><p> Also, the changes described in the second changelog entry below may
cause functions used in index expressions or materialized views to fail
during auto-analyze, or when reloading from a dump. After upgrading,
monitor the server logs for such problems, and fix affected functions.
</p><p> Also, if you are upgrading from a version earlier than 10.2,
see <a class="xref" href="release-10-2.html" title="E.22. Release 10.2">Section E.22</a>.
</p></div><div class="sect2" id="id-1.11.6.25.5"><div class="titlepage"><div><div><h3 class="title">E.21.2. Changes</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> Document how to configure installations and applications to guard
against search-path-dependent trojan-horse attacks from other users
(Noah Misch)
</p><p> Using a <code class="varname">search_path</code> setting that includes any
schemas writable by a hostile user enables that user to capture
control of queries and then run arbitrary SQL code with the
permissions of the attacked user. While it is possible to write
queries that are proof against such hijacking, it is notationally
tedious, and it's very easy to overlook holes. Therefore, we now
recommend configurations in which no untrusted schemas appear in
one's search path. Relevant documentation appears in
<a class="xref" href="ddl-schemas.html#DDL-SCHEMAS-PATTERNS" title="5.8.6. Usage Patterns">Section 5.8.6</a> (for database administrators and users),
<a class="xref" href="libpq-connect.html" title="33.1. Database Connection Control Functions">Section 33.1</a> (for application authors),
<a class="xref" href="extend-extensions.html#EXTEND-EXTENSIONS-SECURITY" title="37.15.6. Security Considerations for Extensions">Section 37.15.6</a> (for extension authors), and
<a class="xref" href="sql-createfunction.html" title="CREATE FUNCTION"><span class="refentrytitle">CREATE FUNCTION</span></a> (for authors
of <code class="literal">SECURITY DEFINER</code> functions).
(CVE-2018-1058)
</p></li><li class="listitem"><p> Avoid use of insecure <code class="varname">search_path</code> settings
in <span class="application">pg_dump</span> and other client programs
(Noah Misch, Tom Lane)
</p><p> <span class="application">pg_dump</span>,
<span class="application">pg_upgrade</span>,
<span class="application">vacuumdb</span> and
other <span class="productname">PostgreSQL</span>-provided applications were
themselves vulnerable to the type of hijacking described in the previous
changelog entry; since these applications are commonly run by
superusers, they present particularly attractive targets. To make them
secure whether or not the installation as a whole has been secured,
modify them to include only the <code class="structname">pg_catalog</code>
schema in their <code class="varname">search_path</code> settings.
Autovacuum worker processes now do the same, as well.
</p><p> In cases where user-provided functions are indirectly executed by
these programs — for example, user-provided functions in index
expressions — the tighter <code class="varname">search_path</code> may
result in errors, which will need to be corrected by adjusting those
user-provided functions to not assume anything about what search path
they are invoked under. That has always been good practice, but now
it will be necessary for correct behavior.
(CVE-2018-1058)
</p></li><li class="listitem"><p> Prevent logical replication from trying to ship changes for
unpublishable relations (Peter Eisentraut)
</p><p> A publication marked <code class="literal">FOR ALL TABLES</code> would
incorrectly ship changes in materialized views
and <code class="structname">information_schema</code> tables, which are
supposed to be omitted from the change stream.
</p></li><li class="listitem"><p> Fix misbehavior of concurrent-update rechecks with CTE references
appearing in subplans (Tom Lane)
</p><p> If a CTE (<code class="literal">WITH</code> clause reference) is used in an
InitPlan or SubPlan, and the query requires a recheck due to trying
to update or lock a concurrently-updated row, incorrect results could
be obtained.
</p></li><li class="listitem"><p> Fix planner failures with overlapping mergejoin clauses in an outer
join (Tom Lane)
</p><p> These mistakes led to <span class="quote">“<span class="quote">left and right pathkeys do not match in
mergejoin</span>”</span> or <span class="quote">“<span class="quote">outer pathkeys do not match
mergeclauses</span>”</span> planner errors in corner cases.
</p></li><li class="listitem"><p> Repair <span class="application">pg_upgrade</span>'s failure to
preserve <code class="structfield">relfrozenxid</code> for materialized
views (Tom Lane, Andres Freund)
</p><p> This oversight could lead to data corruption in materialized views
after an upgrade, manifesting as <span class="quote">“<span class="quote">could not access status of
transaction</span>”</span> or <span class="quote">“<span class="quote">found xmin from before
relfrozenxid</span>”</span> errors. The problem would be more likely to
occur in seldom-refreshed materialized views, or ones that were
maintained only with <code class="command">REFRESH MATERIALIZED VIEW
CONCURRENTLY</code>.
</p><p> If such corruption is observed, it can be repaired by refreshing the
materialized view (without <code class="literal">CONCURRENTLY</code>).
</p></li><li class="listitem"><p> Fix incorrect <span class="application">pg_dump</span> output for some
non-default sequence limit values (Alexey Bashtanov)
</p></li><li class="listitem"><p> Fix <span class="application">pg_dump</span>'s mishandling
of <code class="literal">STATISTICS</code> objects (Tom Lane)
</p><p> An extended statistics object's schema was mislabeled in the dump's
table of contents, possibly leading to the wrong results in a
schema-selective restore. Its ownership was not correctly restored,
either. Also, change the logic so that statistics objects are
dumped/restored, or not, as independent objects rather than tying
them to the dump/restore decision for the table they are on. The
original definition could not scale to the planned future extension to
cross-table statistics.
</p></li><li class="listitem"><p> Fix incorrect reporting of PL/Python function names in
error <code class="literal">CONTEXT</code> stacks (Tom Lane)
</p><p> An error occurring within a nested PL/Python function call (that is,
one reached via a SPI query from another PL/Python function) would
result in a stack trace showing the inner function's name twice,
rather than the expected results. Also, an error in a nested
PL/Python <code class="literal">DO</code> block could result in a null pointer
dereference crash on some platforms.
</p></li><li class="listitem"><p> Allow <code class="filename">contrib/auto_explain</code>'s
<code class="varname">log_min_duration</code> setting to range up
to <code class="literal">INT_MAX</code>, or about 24 days instead of 35 minutes
(Tom Lane)
</p></li><li class="listitem"><p> Mark assorted GUC variables as <code class="literal">PGDLLIMPORT</code>, to
ease porting extension modules to Windows (Metin Doslu)
</p></li></ul></div></div></div><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navfooter"><hr></hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="release-10-4.html" title="E.20. Release 10.4">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="release.html" title="Appendix E. Release Notes">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="release-10-2.html" title="E.22. Release 10.2">Next</a></td></tr><tr><td width="40%" align="left" valign="top">E.20. Release 10.4 </td><td width="20%" align="center"><a accesskey="h" href="index.html" title="PostgreSQL 10.23 Documentation">Home</a></td><td width="40%" align="right" valign="top"> E.22. Release 10.2</td></tr></table></div></body></html>