1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
|
<?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.2. Release 14.4</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-14-5.html" title="E.1. Release 14.5" /><link rel="next" href="release-14-3.html" title="E.3. Release 14.3" /></head><body id="docContent" class="container-fluid col-10"><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">E.2. Release 14.4</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="release-14-5.html" title="E.1. Release 14.5">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 14.5 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="release-14-3.html" title="E.3. Release 14.3">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="RELEASE-14-4"><div class="titlepage"><div><div><h2 class="title" style="clear: both">E.2. Release 14.4</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="sect2"><a href="release-14-4.html#id-1.11.6.6.4">E.2.1. Migration to Version 14.4</a></span></dt><dt><span class="sect2"><a href="release-14-4.html#id-1.11.6.6.5">E.2.2. Changes</a></span></dt></dl></div><p><strong>Release date: </strong>2022-06-16</p><p>
This release contains a variety of fixes from 14.3.
For information about new features in major release 14, see
<a class="xref" href="release-14.html" title="E.6. Release 14">Section E.6</a>.
</p><div class="sect2" id="id-1.11.6.6.4"><div class="titlepage"><div><div><h3 class="title">E.2.1. Migration to Version 14.4</h3></div></div></div><p>
A dump/restore is not required for those running 14.X.
</p><p>
However, if you have any indexes that were created using
the <code class="option">CONCURRENTLY</code> option under 14.X,
you should re-index them after updating.
See the first changelog entry below.
</p><p>
Also, if you are upgrading from a version earlier than 14.3,
see <a class="xref" href="release-14-3.html" title="E.3. Release 14.3">Section E.3</a>.
</p></div><div class="sect2" id="id-1.11.6.6.5"><div class="titlepage"><div><div><h3 class="title">E.2.2. Changes</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Prevent possible corruption of indexes created or rebuilt with
the <code class="literal">CONCURRENTLY</code> option (Álvaro Herrera)
</p><p>
An optimization added in v14 caused <code class="command">CREATE INDEX ...
CONCURRENTLY</code> and <code class="command">REINDEX
... CONCURRENTLY</code> to sometimes miss indexing rows that were
updated during the index build. Revert that optimization.
It is recommended that any indexes made with
the <code class="literal">CONCURRENTLY</code> option be rebuilt after
installing this update. (Alternatively, rebuild them
without <code class="literal">CONCURRENTLY</code>.)
</p></li><li class="listitem"><p>
Harden Memoize plan node against non-deterministic equality
functions (David Rowley)
</p><p>
Memoize could crash if a data type's equality or hash functions gave
inconsistent results across different calls. Throw a runtime error
instead.
</p></li><li class="listitem"><p>
Fix incorrect cost estimates for Memoize plans (David Rowley)
</p><p>
This mistake could lead to Memoize being used when it isn't really
the best plan, or to very long executor startup times due to
initializing an overly-large hash table for a Memoize node.
</p></li><li class="listitem"><p>
Fix queries in which a <span class="quote">“<span class="quote">whole-row variable</span>”</span> references
the result of a function that returns a domain over composite type
(Tom Lane)
</p></li><li class="listitem"><p>
Fix <span class="quote">“<span class="quote">variable not found in subplan target list</span>”</span> planner
error when pulling up a sub-<code class="literal">SELECT</code> that's
referenced in a <code class="literal">GROUPING</code> function (Richard Guo)
</p></li><li class="listitem"><p>
Prevent <code class="function">pg_stat_get_subscription()</code> from
possibly returning an extra row containing garbage values
(Kuntal Ghosh)
</p></li><li class="listitem"><p>
Fix <code class="command">COPY FROM</code>'s error checking in the case where
the database encoding is <code class="literal">SQL_ASCII</code> while the
client's encoding is a multi-byte encoding (Heikki Linnakangas)
</p><p>
This mistake could lead to false complaints of invalidly-encoded
input data.
</p></li><li class="listitem"><p>
Avoid crashing if too many column aliases are attached to
an <code class="literal">XMLTABLE</code> or <code class="literal">JSON_TABLE</code>
construct (Álvaro Herrera)
</p></li><li class="listitem"><p>
When decompiling a view or rule, show a <code class="command">SELECT</code>
output column's <code class="literal">AS "?column?"</code> alias clause
if it could be referenced elsewhere (Tom Lane)
</p><p>
Previously, this auto-generated alias was always hidden; but there
are corner cases where doing so results in a non-restorable view or
rule definition.
</p></li><li class="listitem"><p>
Report implicitly-created operator families to event triggers
(Masahiko Sawada)
</p><p>
If <code class="command">CREATE OPERATOR CLASS</code> results in the implicit
creation of an operator family, that object was not reported to
event triggers that should capture such events.
</p></li><li class="listitem"><p>
Fix control file updates made when a restartpoint is running during
promotion of a standby server (Kyotaro Horiguchi)
</p><p>
Previously, when the restartpoint completed it could incorrectly
update the last-checkpoint fields of the control file, potentially
leading to PANIC and failure to restart if the server crashes before
the next normal checkpoint completes.
</p></li><li class="listitem"><p>
Prevent triggering of
standby's <code class="varname">wal_receiver_timeout</code> during logical
replication of large transactions (Wang Wei, Amit Kapila)
</p><p>
If a large transaction on the primary server sends no data to the
standby (perhaps because no table it changes is published), it was
possible for the standby to timeout. Fix that by ensuring we send
keepalive messages periodically in such situations.
</p></li><li class="listitem"><p>
Prevent open-file leak when reading an invalid timezone abbreviation
file (Kyotaro Horiguchi)
</p><p>
Such cases could result in harmless warning messages.
</p></li><li class="listitem"><p>
Allow custom server parameters to have short descriptions that are
NULL (Steve Chavez)
</p><p>
Previously, although extensions could choose to create such
settings, some code paths would crash while processing them.
</p></li><li class="listitem"><p>
Remove misguided SSL key file ownership check
in <span class="application">libpq</span> (Tom Lane)
</p><p>
In the previous minor releases, we copied the server's permission
checking rules for SSL private key files into libpq. But we should
not have also copied the server's file-ownership check. While that
works in normal use-cases, it can result in an unexpected failure
for clients running as root, and perhaps in other cases.
</p></li><li class="listitem"><p>
Ensure <span class="application">ecpg</span> reports server connection loss
sanely (Tom Lane)
</p><p>
Misprocessing of a libpq-generated error result, such as a report of
lost connection, would lead to printing <span class="quote">“<span class="quote">(null)</span>”</span>
instead of a useful error message; or in older releases it would
lead to a crash.
</p></li><li class="listitem"><p>
Prevent crash after server connection loss
in <span class="application">pg_amcheck</span> (Tom Lane)
</p><p>
Misprocessing of a libpq-generated error result, such as a report of
lost connection, would lead to a crash.
</p></li><li class="listitem"><p>
Adjust PL/Perl test case so it will work under Perl 5.36
(Dagfinn Ilmari Mannsåker)
</p></li><li class="listitem"><p>
Avoid incorrectly using an
out-of-date <span class="application">libldap_r</span> library when
multiple <span class="productname">OpenLDAP</span> installations are
present while building <span class="productname">PostgreSQL</span>
(Tom Lane)
</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-14-5.html" title="E.1. Release 14.5">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-14-3.html" title="E.3. Release 14.3">Next</a></td></tr><tr><td width="40%" align="left" valign="top">E.1. Release 14.5 </td><td width="20%" align="center"><a accesskey="h" href="index.html" title="PostgreSQL 14.5 Documentation">Home</a></td><td width="40%" align="right" valign="top"> E.3. Release 14.3</td></tr></table></div></body></html>
|
