Debian Codegraph @

doc/src/sgml/release-18.sgml

raw
1 <!-- doc/src/sgml/release-18.sgml -->
2 <!-- See header comment in release.sgml about typical markup -->
3
4 <sect1 id="release-18-6">
5 <title>Release 18.6</title>
6
7 <formalpara>
8 <title>Release date:</title>
9 <para>2026-08-13</para>
10 </formalpara>
11
12 <para>
13 This release contains a variety of fixes from 18.4.
14 For information about new features in major release 18, see
15 <xref linkend="release-18"/>.
16 </para>
17
18 <para>
19 Note: 18.5 was never released, due to a regression discovered
20 post-wrap.
21 </para>
22
23 <sect2 id="release-18-6-migration">
24 <title>Migration to Version 18.6</title>
25
26 <para>
27 A dump/restore is not required for those running 18.X.
28 </para>
29
30 <para>
31 However, the first three security entries below describe configuration
32 adjustments and data cleanups that you may need to make after updating.
33 </para>
34
35 <para>
36 Also, if you have any GIN indexes, see the changelog entry below
37 about possibly-corrupt <structfield>reltuples</structfield> values for
38 their tables.
39 </para>
40
41 <para>
42 Also, if you use <filename>contrib/btree_gist</filename>
43 or <filename>contrib/ltree</filename>, you may need to reindex indexes
44 made with those extensions; see the relevant entries below.
45 </para>
46
47 <para>
48 Also, if you are upgrading from a version earlier than 18.2,
49 see <xref linkend="release-18-2"/>.
50 </para>
51 </sect2>
52
53 <sect2 id="release-18-6-changes">
54 <title>Changes</title>
55
56 <itemizedlist>
57
58 <listitem>
59 <!--
60 Author: Jacob Champion <[email protected]>
61 Branch: master [226e49cbe] 2026-08-10 06:37:49 -0700
62 Branch: REL_19_STABLE [5d47df21e] 2026-08-10 06:38:05 -0700
63 Branch: REL_18_STABLE [2a29b607d] 2026-08-10 06:38:12 -0700
64 Branch: REL_17_STABLE [01992176e] 2026-08-10 06:38:18 -0700
65 Branch: REL_16_STABLE [4e1252ee5] 2026-08-10 06:38:24 -0700
66 Branch: REL_15_STABLE [99f205407] 2026-08-10 06:38:30 -0700
67 Branch: REL_14_STABLE [bf3842a64] 2026-08-10 06:38:36 -0700
68 Author: Jacob Champion <[email protected]>
69 Branch: master [20e9dcefd] 2026-08-10 06:37:49 -0700
70 Branch: REL_19_STABLE [7082ce248] 2026-08-10 06:38:05 -0700
71 Branch: REL_18_STABLE [82fd68801] 2026-08-10 06:38:12 -0700
72 Branch: REL_17_STABLE [4fcccea97] 2026-08-10 06:38:18 -0700
73 -->
74 <para>
75 Restrict logical decoding output plugins to the set specified by a
76 new server parameter <varname>output_plugin_libraries</varname>
77 (Jacob Champion)
78 <ulink url="&commit_baseurl;2a29b607d">&sect;</ulink>
79 <ulink url="&commit_baseurl;82fd68801">&sect;</ulink>
80 </para>
81
82 <para>
83 Previously, a replication user could select any loadable library for
84 logical decoding, allowing exploits of various sorts. To allow
85 locking this down without breaking setups that worked before,
86 introduce a whitelist of allowed output plugins.
87 </para>
88
89 <para>
90 By default, only the output plugins shipped as part
91 of <productname>PostgreSQL</productname>
92 (<literal>pgoutput</literal> and <literal>test_decoding</literal>)
93 are included in <varname>output_plugin_libraries</varname>.
94 Installations that rely on other output plugins must add them
95 after updating the server, for example
96 <programlisting>
97 output_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder'
98 </programlisting>
99 </para>
100
101 <para>
102 Additionally, <command>pg_upgrade --check</command> will fail if the
103 <varname>output_plugin_libraries</varname> parameter on the new
104 cluster does not permit the plugins of logical replication slots
105 on the old cluster, when migrating from versions 17 and later.
106 Make necessary additions to the new cluster's setting before
107 performing <application>pg_upgrade</application>.
108 </para>
109
110 <para>
111 The <productname>PostgreSQL</productname> Project thanks
112 Vladimir Tokarev and Yu Kunpeng
113 for reporting this problem.
114 (CVE-2026-6471)
115 </para>
116 </listitem>
117
118 <listitem>
119 <!--
120 Author: Daniel Gustafsson <[email protected]>
121 Branch: master [d0ecee6de] 2026-08-10 06:37:50 -0700
122 Branch: REL_19_STABLE [ba207f58f] 2026-08-10 06:38:06 -0700
123 Branch: REL_18_STABLE [fe32b10fc] 2026-08-10 06:38:13 -0700
124 Branch: REL_17_STABLE [b05cfc693] 2026-08-10 06:38:19 -0700
125 Branch: REL_16_STABLE [6ca6023ca] 2026-08-10 06:38:25 -0700
126 Branch: REL_15_STABLE [472ef7e4a] 2026-08-10 06:38:31 -0700
127 Branch: REL_14_STABLE [7e29eb6f4] 2026-08-10 06:38:37 -0700
128 Author: Jacob Champion <[email protected]>
129 Branch: master [49e795414] 2026-08-10 06:37:50 -0700
130 Branch: REL_19_STABLE [d97b3f58c] 2026-08-10 06:38:06 -0700
131 Branch: REL_18_STABLE [4c5128ca0] 2026-08-10 06:38:13 -0700
132 Branch: REL_17_STABLE [7eed42aa8] 2026-08-10 06:38:19 -0700
133 Branch: REL_16_STABLE [ba2a63faf] 2026-08-10 06:38:25 -0700
134 Branch: REL_15_STABLE [953be116c] 2026-08-10 06:38:31 -0700
135 Branch: REL_14_STABLE [e2c48c81f] 2026-08-10 06:38:37 -0700
136 -->
137 <para>
138 Fix <filename>contrib/pgcrypto</filename>'s PGP encryption to detect
139 unsupported ciphers (Daniel Gustafsson)
140 <ulink url="&commit_baseurl;fe32b10fc">&sect;</ulink>
141 <ulink url="&commit_baseurl;4c5128ca0">&sect;</ulink>
142 </para>
143
144 <para>
145 Previously, if OpenSSL rejected the requested cipher (for example,
146 because it is running in FIPS mode, or the legacy provider hasn't
147 been loaded), <application>pgcrypto</application> failed to notice
148 the failure and simply XOR'd the non-encrypted block with the
149 plaintext, rendering the <quote>encryption</quote> trivially
150 breakable. This will typically occur with deprecated or non-FIPS
151 cipher algorithms (cipher-algo=blowfish/bf, twofish, cast5, or
152 3des).
153 </para>
154
155 <para>
156 By default, <application>pgcrypto</application> will now fail to
157 decrypt any messages that were affected in this way. To allow
158 retrieval of such data, a new
159 option <literal>ignore-cipher-failure</literal> has been added
160 to <function>pgp_pub_decrypt()</function>
161 and <function>pgp_sym_decrypt()</function>.
162 Setting <literal>ignore-cipher-failure=1</literal> will restore
163 their previous behavior, allowing the faulty encryption wrapper to
164 be stripped off:
165 <programlisting>
166 pgp_sym_decrypt(encrypted_column, <replaceable>any key</replaceable>, 'ignore-cipher-failure=1')
167 </programlisting>
168 Once the affected messages are identified and stripped of their
169 wrappers, they can then be re-encrypted with a modern algorithm. It
170 is important however that the behavior of OpenSSL be the same as it
171 was when the faulty messages were created: if the set of unsupported
172 algorithms is not the same, this approach will not work. See the
173 documentation for <literal>ignore-cipher-failure</literal>.
174 </para>
175
176 <para>
177 The <productname>PostgreSQL</productname> Project thanks
178 Shishir Sharma
179 for reporting this problem.
180 (CVE-2026-14663)
181 </para>
182 </listitem>
183
184 <listitem>
185 <!--
186 Author: Tom Lane <[email protected]>
187 Branch: master [3045a25ba] 2026-08-10 06:37:50 -0700
188 Branch: REL_19_STABLE [d6ab88d37] 2026-08-10 06:38:06 -0700
189 Branch: REL_18_STABLE [29921259e] 2026-08-10 06:38:13 -0700
190 Branch: REL_17_STABLE [46fa1f6f3] 2026-08-10 06:38:19 -0700
191 Branch: REL_16_STABLE [2bdfd5cdc] 2026-08-10 06:38:25 -0700
192 Branch: REL_15_STABLE [3fdcfa8f7] 2026-08-10 06:38:31 -0700
193 Branch: REL_14_STABLE [5c51ae455] 2026-08-10 06:38:36 -0700
194 Branch: master [cf754f741] 2026-08-10 06:37:50 -0700
195 Branch: REL_19_STABLE [8cf01e213] 2026-08-10 06:38:06 -0700
196 Branch: REL_18_STABLE [900894d35] 2026-08-10 06:38:13 -0700
197 Branch: REL_17_STABLE [dca6627de] 2026-08-10 06:38:19 -0700
198 Branch: REL_16_STABLE [db96e87f9] 2026-08-10 06:38:25 -0700
199 Branch: REL_15_STABLE [8cdbabea7] 2026-08-10 06:38:31 -0700
200 Branch: REL_14_STABLE [7215c7e96] 2026-08-10 06:38:36 -0700
201 -->
202 <para>
203 Fix <application>psql</application> to skip in-line data following a
204 scripted <command>COPY ... FROM STDIN</command> command, even if
205 the <command>COPY</command> fails before
206 sending <literal>PGRES_COPY_IN</literal> (Tom Lane)
207 <ulink url="&commit_baseurl;29921259e">&sect;</ulink>
208 <ulink url="&commit_baseurl;900894d35">&sect;</ulink>
209 </para>
210
211 <para>
212 Previously, if a <literal>COPY</literal> command failed at startup
213 (for instance, because the target table doesn't exist)
214 <application>psql</application> would not realize that and would
215 proceed to read the following in-line data as SQL commands. In the
216 best case that's wrong and in the worst case it's a SQL-injection
217 hazard. Teach <application>psql</application> to recognize
218 syntactically-valid <command>COPY ... FROM STDIN</command> commands
219 and to skip data on its own authority if the server doesn't respond
220 with <literal>PGRES_COPY_IN</literal>.
221 </para>
222
223 <para>
224 While this fix is unlikely to affect any production SQL scripts,
225 test scripts might intentionally exercise failing <command>COPY
226 ... FROM STDIN</command> commands. Those will need to gain
227 a <literal>\.</literal> data terminator line after each such
228 command.
229 </para>
230
231 <para>
232 The <productname>PostgreSQL</productname> Project thanks
233 Alexander Lakhin
234 for reporting this problem.
235 (CVE-2026-6464)
236 </para>
237 </listitem>
238
239 <listitem>
240 <!--
241 Author: Robert Haas <[email protected]>
242 Branch: master [9e02e2e18] 2026-08-10 06:37:49 -0700
243 Branch: REL_19_STABLE [64a65ead1] 2026-08-10 06:38:05 -0700
244 Branch: REL_18_STABLE [37b8f3b0e] 2026-08-10 06:38:12 -0700
245 Branch: REL_17_STABLE [60887d348] 2026-08-10 06:38:18 -0700
246 Branch: REL_16_STABLE [7d150b5c9] 2026-08-10 06:38:24 -0700
247 Branch: REL_15_STABLE [fc933ce00] 2026-08-10 06:38:30 -0700
248 Branch: REL_14_STABLE [1f49beef2] 2026-08-10 06:38:36 -0700
249 -->
250 <para>
251 Cross-check the output row type of a portal
252 running <command>EXECUTE</command> or <command>FETCH</command>
253 (Robert Haas)
254 <ulink url="&commit_baseurl;37b8f3b0e">&sect;</ulink>
255 </para>
256
257 <para>
258 <command>EXECUTE</command> and <command>FETCH</command> use two
259 portals: an outer one for the statement itself, and an inner one
260 running the query being executed on its behalf. It was previously
261 possible to make the declared row types of the two portals diverge,
262 leading to server memory disclosure and arbitrary code execution.
263 </para>
264
265 <para>
266 The <productname>PostgreSQL</productname> Project thanks
267 Ben Morris (in collaboration with Claude and Anthropic Research)
268 and Peter Geoghegan
269 for reporting this problem.
270 (CVE-2026-16239)
271 </para>
272 </listitem>
273
274 <listitem>
275 <!--
276 Author: Tom Lane <[email protected]>
277 Branch: master [3d724bf4f] 2026-08-10 06:37:47 -0700
278 Branch: REL_19_STABLE [3294ab839] 2026-08-10 06:38:03 -0700
279 Branch: REL_18_STABLE [4fafe2380] 2026-08-10 06:38:10 -0700
280 Branch: REL_17_STABLE [12a620686] 2026-08-10 06:38:17 -0700
281 Author: Álvaro Herrera <[email protected]>
282 Branch: REL_16_STABLE [5dbeb69bc] 2026-07-29 17:15:45 +0200
283 Branch: REL_15_STABLE [8f64cc83f] 2026-07-29 17:15:45 +0200
284 Branch: REL_14_STABLE [5fb3c6389] 2026-07-29 17:15:45 +0200
285 -->
286 <para>
287 Fix buffer overrun with long time zone abbreviation in
288 <function>to_char()</function> (Tom Lane)
289 <ulink url="&commit_baseurl;4fafe2380">&sect;</ulink>
290 </para>
291
292 <para>
293 This can easily crash the server, and exploits leading to arbitrary
294 code execution have been reported.
295 </para>
296
297 <para>
298 The <productname>PostgreSQL</productname> Project thanks
299 Hcamael, Amjad Shahzad, Tan Zhen of AntAISecurityLab, Tomer Fichman,
300 Zheng Yu, Amy Burnett (OpenAI Codex Security), Rick de Jager, Heewon
301 Song, Sylvie Mayer, Aleksander Alekseev, and Hillai Ben Sasson
302 for reporting this problem.
303 (CVE-2026-14669)
304 </para>
305 </listitem>
306
307 <listitem>
308 <!--
309 Author: Masahiko Sawada <[email protected]>
310 Branch: master [343aabf1d] 2026-08-10 06:37:48 -0700
311 Branch: REL_19_STABLE [7df2aa8ef] 2026-08-10 06:38:04 -0700
312 Branch: REL_18_STABLE [b7e5c3f63] 2026-08-10 06:38:10 -0700
313 Branch: REL_17_STABLE [e91dcfcca] 2026-08-10 06:38:17 -0700
314 Branch: REL_16_STABLE [3179253c2] 2026-08-10 06:38:23 -0700
315 Branch: REL_15_STABLE [127a0673f] 2026-08-10 06:38:29 -0700
316 Branch: REL_14_STABLE [890327639] 2026-08-10 06:38:35 -0700
317 -->
318 <para>
319 Fix buffer overrun in regexp match/split functions (Masahiko Sawada)
320 <ulink url="&commit_baseurl;b7e5c3f63">&sect;</ulink>
321 </para>
322
323 <para>
324 If passed invalidly-encoded data, these functions could write past
325 the end of their conversion buffer.
326 </para>
327
328 <para>
329 The <productname>PostgreSQL</productname> Project thanks
330 Francesco Verardi
331 for reporting this problem.
332 (CVE-2026-14664)
333 </para>
334 </listitem>
335
336 <listitem>
337 <!--
338 Author: Michael Paquier <[email protected]>
339 Branch: master [a16c31d39] 2026-08-10 06:37:50 -0700
340 Branch: REL_19_STABLE [80ce920a5] 2026-08-10 06:38:06 -0700
341 Branch: REL_18_STABLE [08e812c02] 2026-08-10 06:38:13 -0700
342 Branch: REL_17_STABLE [849da8210] 2026-08-10 06:38:19 -0700
343 Branch: REL_16_STABLE [ac450853d] 2026-08-10 06:38:25 -0700
344 Branch: REL_15_STABLE [3b925133b] 2026-08-10 06:38:31 -0700
345 Branch: REL_14_STABLE [42d333a78] 2026-08-10 06:38:36 -0700
346 -->
347 <para>
348 Harden the <function>ascii()</function> function against invalid
349 input (Michael Paquier)
350 <ulink url="&commit_baseurl;08e812c02">&sect;</ulink>
351 </para>
352
353 <para>
354 By supplying invalidly-encoded input, this function could be coaxed
355 to read and return a few bytes of data that it shouldn't. In
356 assert-enabled builds, its assertions could be triggered too.
357 </para>
358
359 <para>
360 The <productname>PostgreSQL</productname> Project thanks
361 Hcamael
362 for reporting this problem.
363 (CVE-2026-18024)
364 </para>
365 </listitem>
366
367 <listitem>
368 <!--
369 Author: Michael Paquier <[email protected]>
370 Branch: master [57835938f] 2026-08-10 06:37:49 -0700
371 Branch: REL_19_STABLE [b3d9262bb] 2026-08-10 06:38:05 -0700
372 Branch: REL_18_STABLE [08454e8b2] 2026-08-10 06:38:12 -0700
373 Branch: REL_18_STABLE [8d428c6e6] 2026-08-10 06:38:12 -0700
374 -->
375 <para>
376 Fix multirange type handling
377 in <function>pg_restore_attribute_stats()</function>
378 (OpenAI Security Research Team)
379 <ulink url="&commit_baseurl;08454e8b2">&sect;</ulink>
380 <ulink url="&commit_baseurl;8d428c6e6">&sect;</ulink>
381 </para>
382
383 <para>
384 <function>pg_restore_attribute_stats()</function> treated multirange
385 types just like their underlying range type. This works correctly
386 for the bounds histogram, but it was wrong for all the other
387 statistics kinds.
388 </para>
389
390 <para>
391 The <productname>PostgreSQL</productname> Project thanks
392 Amy Burnett (OpenAI Codex Security)
393 for reporting this problem.
394 (CVE-2026-16238)
395 </para>
396 </listitem>
397
398 <listitem>
399 <!--
400 Author: Tom Lane <[email protected]>
401 Branch: master [8f0c3d2fe] 2026-08-10 06:37:48 -0700
402 Branch: REL_19_STABLE [0d60ee717] 2026-08-10 06:38:04 -0700
403 Branch: REL_18_STABLE [a2cb5a1cf] 2026-08-10 06:38:11 -0700
404 Branch: REL_17_STABLE [0ebf896f4] 2026-08-10 06:38:17 -0700
405 Branch: REL_16_STABLE [591192e2e] 2026-08-10 06:38:23 -0700
406 Branch: REL_15_STABLE [005ffaa7f] 2026-08-10 06:38:29 -0700
407 Branch: REL_14_STABLE [59205c7e9] 2026-08-10 06:38:35 -0700
408 -->
409 <para>
410 Make <function>scalarineqsel()</function> check that a constant it
411 expects to be of type <type>tid</type> actually is (Tom Lane)
412 <ulink url="&commit_baseurl;a2cb5a1cf">&sect;</ulink>
413 </para>
414
415 <para>
416 This expectation will hold for all the built-in operators that use
417 this estimator, but a maliciously-constructed operator could violate
418 it, leading to a crash or server memory disclosure.
419 </para>
420
421 <para>
422 The <productname>PostgreSQL</productname> Project thanks
423 Hcamael
424 for reporting this problem.
425 (CVE-2026-14668)
426 </para>
427 </listitem>
428
429 <listitem>
430 <!--
431 Author: Tom Lane <[email protected]>
432 Branch: master [23d9ad771] 2026-08-10 06:37:47 -0700
433 Branch: REL_19_STABLE [cb947ca31] 2026-08-10 06:38:03 -0700
434 Branch: REL_18_STABLE [e25135057] 2026-08-10 06:38:10 -0700
435 Branch: REL_17_STABLE [fe0b5bd6d] 2026-08-10 06:38:17 -0700
436 Branch: REL_16_STABLE [7c1a8805a] 2026-08-10 06:38:23 -0700
437 Branch: REL_15_STABLE [f443d0a0a] 2026-08-10 06:38:29 -0700
438 Branch: REL_14_STABLE [7c2ba321d] 2026-08-10 06:38:34 -0700
439 Branch: master [90649b6f8] 2026-08-10 06:37:47 -0700
440 Branch: REL_19_STABLE [3b2238fbe] 2026-08-10 06:38:03 -0700
441 Branch: REL_18_STABLE [dddc8a69f] 2026-08-10 06:38:10 -0700
442 Branch: REL_17_STABLE [8e87bd473] 2026-08-10 06:38:17 -0700
443 Branch: REL_16_STABLE [84b6a7a06] 2026-08-10 06:38:23 -0700
444 Branch: REL_15_STABLE [4f8b37b6b] 2026-08-10 06:38:29 -0700
445 Branch: REL_14_STABLE [1e3014f37] 2026-08-10 06:38:34 -0700
446 -->
447 <para>
448 Harden <type>tsvector</type> and <type>tsquery</type> code against
449 overly long values (both individual lexemes and total vector/query
450 length) (Tom Lane)
451 <ulink url="&commit_baseurl;e25135057">&sect;</ulink>
452 <ulink url="&commit_baseurl;dddc8a69f">&sect;</ulink>
453 </para>
454
455 <para>
456 The documented limits were not enforced in all code paths.
457 </para>
458
459 <para>
460 The <productname>PostgreSQL</productname> Project thanks
461 Yuhang Wu, Zhenpeng Lin, Zheng Yu, and Hcamael
462 for reporting these problems.
463 (CVE-2026-14662)
464 </para>
465 </listitem>
466
467 <listitem>
468 <!--
469 Author: Tom Lane <[email protected]>
470 Branch: master [7bd56f7a3] 2026-08-10 06:37:48 -0700
471 Branch: REL_19_STABLE [92972e815] 2026-08-10 06:38:04 -0700
472 Branch: REL_18_STABLE [7f0e1aac7] 2026-08-10 06:38:11 -0700
473 Branch: REL_17_STABLE [797e3cc4c] 2026-08-10 06:38:17 -0700
474 Branch: REL_16_STABLE [8c67c4cf5] 2026-08-10 06:38:23 -0700
475 Branch: REL_15_STABLE [b417744a7] 2026-08-10 06:38:29 -0700
476 Branch: REL_14_STABLE [cf44ff5e6] 2026-08-10 06:38:35 -0700
477 Branch: master [60e7329b9] 2026-08-10 06:37:48 -0700
478 Branch: REL_19_STABLE [42d9749b7] 2026-08-10 06:38:04 -0700
479 Branch: REL_18_STABLE [2a03f21da] 2026-08-10 06:38:11 -0700
480 Branch: REL_17_STABLE [8a40f4b09] 2026-08-10 06:38:17 -0700
481 Branch: REL_16_STABLE [32e0d25d4] 2026-08-10 06:38:23 -0700
482 Branch: REL_15_STABLE [eb2fa2704] 2026-08-10 06:38:29 -0700
483 Branch: REL_14_STABLE [c7f462838] 2026-08-10 06:38:35 -0700
484 -->
485 <para>
486 Fix various places that mistakenly assumed they would not have to
487 deal with more than <literal>FUNC_MAX_ARGS</literal> function
488 arguments (Tom Lane)
489 <ulink url="&commit_baseurl;7f0e1aac7">&sect;</ulink>
490 <ulink url="&commit_baseurl;2a03f21da">&sect;</ulink>
491 </para>
492
493 <para>
494 Notably, the server's actual limit on the number of arguments to an
495 aggregate function is <literal>FUNC_MAX_ARGS - 1</literal>, but the
496 parser failed to enforce that, creating hazards downstream.
497 </para>
498
499 <para>
500 The <productname>PostgreSQL</productname> Project thanks
501 Zheng Yu, ylwangtju, and Masahiko Sawada
502 for reporting these problems.
503 (CVE-2026-14679)
504 </para>
505 </listitem>
506
507 <listitem>
508 <!--
509 Author: Tom Lane <[email protected]>
510 Branch: master [8f7e35b08] 2026-08-10 06:37:48 -0700
511 Branch: REL_19_STABLE [21a00de43] 2026-08-10 06:38:04 -0700
512 Branch: REL_18_STABLE [54649de65] 2026-08-10 06:38:11 -0700
513 Branch: REL_17_STABLE [eb9e55297] 2026-08-10 06:38:17 -0700
514 Branch: REL_16_STABLE [4c0c1b2cd] 2026-08-10 06:38:23 -0700
515 Branch: REL_15_STABLE [e926a9aac] 2026-08-10 06:38:29 -0700
516 Branch: REL_14_STABLE [155dacbc5] 2026-08-10 06:38:35 -0700
517 Branch: master [1aa601b4f] 2026-08-10 06:37:48 -0700
518 Branch: REL_19_STABLE [21d8cfb18] 2026-08-10 06:38:04 -0700
519 Branch: REL_18_STABLE [722695db1] 2026-08-10 06:38:11 -0700
520 Branch: REL_17_STABLE [83d0a083f] 2026-08-10 06:38:18 -0700
521 Branch: REL_16_STABLE [7f308dd7c] 2026-08-10 06:38:23 -0700
522 Branch: REL_15_STABLE [d6e861e19] 2026-08-10 06:38:29 -0700
523 Branch: REL_14_STABLE [913fe0c31] 2026-08-10 06:38:35 -0700
524 -->
525 <para>
526 Reject calls from SQL to functions that take or return
527 type <type>internal</type> (Tom Lane)
528 <ulink url="&commit_baseurl;54649de65">&sect;</ulink>
529 <ulink url="&commit_baseurl;722695db1">&sect;</ulink>
530 </para>
531
532 <para>
533 The existing defenses against doing this have been shown to be
534 insufficient, so add more explicit checks.
535 </para>
536
537 <para>
538 The <productname>PostgreSQL</productname> Project thanks
539 Amy Burnett (OpenAI Codex Security)
540 for reporting this problem.
541 (CVE-2026-14680)
542 </para>
543 </listitem>
544
545 <listitem>
546 <!--
547 Author: Masahiko Sawada <[email protected]>
548 Branch: master [6713a6e04] 2026-08-10 06:37:48 -0700
549 Branch: REL_19_STABLE [93b93f28f] 2026-08-10 06:38:04 -0700
550 Branch: REL_18_STABLE [a1fa24127] 2026-08-10 06:38:11 -0700
551 Branch: REL_17_STABLE [75a03c569] 2026-08-10 06:38:18 -0700
552 Branch: REL_16_STABLE [7c3367ab5] 2026-08-10 06:38:24 -0700
553 Branch: REL_15_STABLE [fb6d1ca8d] 2026-08-10 06:38:29 -0700
554 Branch: REL_14_STABLE [70a3b4e18] 2026-08-10 06:38:35 -0700
555 -->
556 <para>
557 Preserve the ownership of extended statistics objects when they are
558 rebuilt by <command>ALTER TABLE</command> (Masahiko Sawada)
559 <ulink url="&commit_baseurl;a1fa24127">&sect;</ulink>
560 </para>
561
562 <para>
563 Previously, the role running <command>ALTER TABLE</command> gained
564 ownership of such objects, but that seems inappropriate.
565 </para>
566
567 <para>
568 The <productname>PostgreSQL</productname> Project thanks
569 Noah Misch
570 for reporting this problem.
571 (CVE-2026-6469)
572 </para>
573 </listitem>
574
575 <listitem>
576 <!--
577 Author: Nathan Bossart <[email protected]>
578 Branch: master [f9729b507] 2026-08-10 06:37:49 -0700
579 Branch: REL_19_STABLE [a3832a757] 2026-08-10 06:38:05 -0700
580 Branch: REL_18_STABLE [0ddd9098a] 2026-08-10 06:38:12 -0700
581 Branch: REL_17_STABLE [5981fe370] 2026-08-10 06:38:18 -0700
582 Branch: REL_16_STABLE [5e5ea74e3] 2026-08-10 06:38:24 -0700
583 Branch: REL_15_STABLE [44ea6764b] 2026-08-10 06:38:30 -0700
584 Branch: REL_14_STABLE [967acab87] 2026-08-10 06:38:35 -0700
585 -->
586 <para>
587 When deparsing an <function>EXTRACT()</function> function call,
588 quote the field name if needed (Nathan Bossart)
589 <ulink url="&commit_baseurl;0ddd9098a">&sect;</ulink>
590 </para>
591
592 <para>
593 The parser accepts any string literal as a field name
594 in <function>EXTRACT()</function>, deferring validation to
595 execution. If the call is stored and deparsed (for example
596 during <application>pg_dump</application>), the string body was
597 regurgitated verbatim, allowing SQL injection.
598 </para>
599
600 <para>
601 The <productname>PostgreSQL</productname> Project thanks
602 Ben Morris (in collaboration with Claude and Anthropic Research)
603 for reporting this problem.
604 (CVE-2026-15741)
605 </para>
606 </listitem>
607
608 <listitem>
609 <!--
610 Author: Nathan Bossart <[email protected]>
611 Branch: master [a9f6e768a] 2026-08-10 06:37:49 -0700
612 Branch: REL_19_STABLE [efdb26072] 2026-08-10 06:38:05 -0700
613 Branch: REL_18_STABLE [2e91f8548] 2026-08-10 06:38:12 -0700
614 Branch: REL_17_STABLE [fd6d3e7e9] 2026-08-10 06:38:19 -0700
615 Branch: REL_16_STABLE [24855357c] 2026-08-10 06:38:24 -0700
616 Branch: REL_15_STABLE [97e277402] 2026-08-10 06:38:30 -0700
617 Branch: REL_14_STABLE [323af0a4e] 2026-08-10 06:38:36 -0700
618 Branch: master [53ed5ebd8] 2026-08-10 06:37:50 -0700
619 Branch: REL_19_STABLE [bb1bc525d] 2026-08-10 06:38:06 -0700
620 Branch: REL_18_STABLE [57f59ca1d] 2026-08-10 06:38:12 -0700
621 Branch: REL_17_STABLE [671359605] 2026-08-10 06:38:19 -0700
622 Branch: REL_16_STABLE [7a761fe40] 2026-08-10 06:38:25 -0700
623 Branch: REL_15_STABLE [c062734cd] 2026-08-10 06:38:30 -0700
624 Branch: REL_14_STABLE [b6e45b4f8] 2026-08-10 06:38:36 -0700
625 Branch: master [4fac4c108] 2026-08-10 06:37:50 -0700
626 Branch: REL_19_STABLE [424fb7160] 2026-08-10 06:38:06 -0700
627 Branch: REL_18_STABLE [278053843] 2026-08-10 06:38:12 -0700
628 Branch: REL_17_STABLE [d1c8aa0b0] 2026-08-10 06:38:19 -0700
629 Branch: REL_16_STABLE [7ce056b17] 2026-08-10 06:38:24 -0700
630 Branch: REL_15_STABLE [6dbedd48b] 2026-08-10 06:38:30 -0700
631 Branch: REL_14_STABLE [1a358b8f2] 2026-08-10 06:38:36 -0700
632 -->
633 <para>
634 Check for <literal>USAGE</literal> privilege on data types in places
635 that formerly failed to check that (Nathan Bossart)
636 <ulink url="&commit_baseurl;2e91f8548">&sect;</ulink>
637 <ulink url="&commit_baseurl;57f59ca1d">&sect;</ulink>
638 <ulink url="&commit_baseurl;278053843">&sect;</ulink>
639 </para>
640
641 <para>
642 <command>CREATE TYPE AS RANGE</command> did not check, nor
643 did <command>ALTER TABLE OF</command>, nor did commands that create
644 stored expressions. These omissions allowed roles
645 without <literal>USAGE</literal> privilege to nonetheless create
646 objects depending on the type, possibly blocking the type's owner
647 from changing the type later.
648 </para>
649
650 <para>
651 The <productname>PostgreSQL</productname> Project thanks
652 Jingzhou Fu
653 for reporting this problem.
654 (CVE-2026-6470)
655 </para>
656 </listitem>
657
658 <listitem>
659 <!--
660 Author: Nathan Bossart <[email protected]>
661 Branch: master [ffca23839] 2026-08-10 06:37:50 -0700
662 Branch: REL_19_STABLE [567286b76] 2026-08-10 06:38:06 -0700
663 Branch: REL_18_STABLE [0b12f56bf] 2026-08-10 06:38:13 -0700
664 Branch: REL_17_STABLE [1974acf23] 2026-08-10 06:38:19 -0700
665 Branch: REL_16_STABLE [f5f2da795] 2026-08-10 06:38:25 -0700
666 Branch: REL_15_STABLE [17b6083db] 2026-08-10 06:38:30 -0700
667 Branch: REL_14_STABLE [f4174aa84] 2026-08-10 06:38:36 -0700
668 -->
669 <para>
670 Invalidate role-dependent cached plans after role changes
671 (Ilya Staroverov, Shinya Kato, Nathan Bossart)
672 <ulink url="&commit_baseurl;0b12f56bf">&sect;</ulink>
673 </para>
674
675 <para>
676 Role membership, role attribute, and database ownership changes may
677 impact the expected behavior of row-level security policies, but
678 previously we'd continue to use cached plans that were made
679 according to the old state of affairs.
680 </para>
681
682 <para>
683 The <productname>PostgreSQL</productname> Project thanks
684 Ilya Staroverov and Shinya Kato
685 for reporting this problem.
686 (CVE-2026-14666)
687 </para>
688 </listitem>
689
690 <listitem>
691 <!--
692 Author: Michael Paquier <[email protected]>
693 Branch: master [3bf185b4b] 2026-08-10 06:37:49 -0700
694 Branch: REL_19_STABLE [bf1bb7e29] 2026-08-10 06:38:05 -0700
695 Branch: REL_18_STABLE [203a48209] 2026-08-10 06:38:11 -0700
696 Branch: REL_17_STABLE [067a64d40] 2026-08-10 06:38:18 -0700
697 -->
698 <para>
699 Reject GSSEncRequest after direct SSL connection (Michael Paquier)
700 <ulink url="&commit_baseurl;203a48209">&sect;</ulink>
701 </para>
702
703 <para>
704 After establishing a TLS-encrypted connection, the server would
705 still accept a request for GSSAPI encryption. If that succeeded,
706 the connection would proceed using TLS encryption, but it would look
707 like a GSS connection to the <filename>pg_hba</filename> rules.
708 Thus, a <filename>pg_hba</filename> policy intending to disallow TLS
709 would not be enforced correctly.
710 </para>
711
712 <para>
713 The <productname>PostgreSQL</productname> Project thanks
714 p4p3r
715 for reporting this problem.
716 (CVE-2026-14681)
717 </para>
718 </listitem>
719
720 <listitem>
721 <!--
722 Author: Nathan Bossart <[email protected]>
723 Branch: master [feb8b0182] 2026-08-10 06:37:49 -0700
724 Branch: REL_19_STABLE [4d192fa16] 2026-08-10 06:38:05 -0700
725 Branch: REL_18_STABLE [822143c4d] 2026-08-10 06:38:12 -0700
726 Branch: REL_17_STABLE [dec60e8ad] 2026-08-10 06:38:18 -0700
727 Branch: REL_16_STABLE [fadbe882d] 2026-08-10 06:38:24 -0700
728 -->
729 <para>
730 Make mock SCRAM authentication secrets more plausible (Nathan Bossart)
731 <ulink url="&commit_baseurl;822143c4d">&sect;</ulink>
732 </para>
733
734 <para>
735 If a SCRAM login is attempted against a role that doesn't exist or
736 doesn't have a SCRAM secret, we generate a mock secret and carry out
737 the authentication handshake anyway, to avoid revealing these facts
738 to an attacker. But the mock secret was made with a fixed iteration
739 count, which in itself can be an observable response discrepancy.
740 Use the configuration setting <varname>scram_iterations</varname>
741 instead, to make the mock secret look more like the installation's
742 real secrets.
743 </para>
744
745 <para>
746 The <productname>PostgreSQL</productname> Project thanks
747 Radim Marek
748 for reporting this problem.
749 (CVE-2026-14672)
750 </para>
751 </listitem>
752
753 <listitem>
754 <!--
755 Author: Michael Paquier <[email protected]>
756 Branch: master [c7da85fec] 2026-08-10 06:37:49 -0700
757 Branch: REL_19_STABLE [457b8737a] 2026-08-10 06:38:05 -0700
758 Branch: REL_18_STABLE [a14ba29b1] 2026-08-10 06:38:11 -0700
759 Branch: REL_17_STABLE [c3c830272] 2026-08-10 06:38:18 -0700
760 Branch: REL_16_STABLE [39f855e0e] 2026-08-10 06:38:24 -0700
761 Branch: REL_15_STABLE [5737110b6] 2026-08-10 06:38:30 -0700
762 Branch: REL_14_STABLE [74c59d062] 2026-08-10 06:38:35 -0700
763 -->
764 <para>
765 Fix out-of-bounds writes in <application>ecpg</application>
766 applications caused by invalid <type>bytea</type> data received from
767 the server (Michael Paquier)
768 <ulink url="&commit_baseurl;a14ba29b1">&sect;</ulink>
769 </para>
770
771 <para>
772 <application>ecpg</application> assumed without checking that
773 any <type>bytea</type> value must begin with <literal>\x</literal>.
774 A broken or malicious server might send a string shorter than 2
775 bytes, resulting in memory clobber in the application.
776 </para>
777
778 <para>
779 The <productname>PostgreSQL</productname> Project thanks
780 ylwangtju
781 for reporting this problem.
782 (CVE-2026-16241)
783 </para>
784 </listitem>
785
786 <listitem>
787 <!--
788 Author: Nathan Bossart <[email protected]>
789 Branch: master [086f6f176] 2026-08-10 06:37:50 -0700
790 Branch: REL_19_STABLE [0119aa30e] 2026-08-10 06:38:06 -0700
791 Branch: REL_18_STABLE [71ca694c7] 2026-08-10 06:38:13 -0700
792 Branch: REL_17_STABLE [0bfac9e1f] 2026-08-10 06:38:19 -0700
793 Branch: REL_16_STABLE [33d0c63fb] 2026-08-10 06:38:25 -0700
794 Branch: REL_15_STABLE [df245c374] 2026-08-10 06:38:31 -0700
795 Branch: REL_14_STABLE [2006fca40] 2026-08-10 06:38:37 -0700
796 -->
797 <para>
798 Do not do backquote expansion on the argument
799 of <application>psql</application>'s <command>\unrestrict</command>
800 command (Nathan Bossart)
801 <ulink url="&commit_baseurl;71ca694c7">&sect;</ulink>
802 </para>
803
804 <para>
805 This oversight in the fix for CVE-2025-8714 allows a malicious
806 server to inject shell commands into plain-text dump output that
807 will be run at restore time on the machine
808 running <application>psql</application>, the exact scenario that
809 CVE-2025-8714 intended to prevent.
810 </para>
811
812 <para>
813 The <productname>PostgreSQL</productname> Project thanks
814 Lucas Velgus, Filip Janus, and Daniel Bakker
815 for reporting this problem.
816 (CVE-2026-18408)
817 </para>
818 </listitem>
819
820 <listitem>
821 <!--
822 Author: Tom Lane <[email protected]>
823 Branch: master [13bb73aeb] 2026-08-10 06:37:48 -0700
824 Branch: REL_19_STABLE [86cd82bf4] 2026-08-10 06:38:04 -0700
825 Branch: REL_18_STABLE [3392cce5c] 2026-08-10 06:38:11 -0700
826 Branch: REL_17_STABLE [c2b16f5d4] 2026-08-10 06:38:17 -0700
827 Branch: REL_16_STABLE [3299c2ba0] 2026-08-10 06:38:23 -0700
828 Branch: REL_15_STABLE [71ba5705d] 2026-08-10 06:38:29 -0700
829 Branch: REL_14_STABLE [57aa21f69] 2026-08-10 06:38:35 -0700
830 -->
831 <para>
832 Remove <application>pg_dump</application>'s assumption that
833 <structname>pg_proc</structname>.<structfield>protrftypes</structfield>
834 cannot have more than <literal>FUNC_MAX_ARGS</literal> entries
835 (Tom Lane)
836 <ulink url="&commit_baseurl;3392cce5c">&sect;</ulink>
837 </para>
838
839 <para>
840 Since there could be entries for both input and output arguments,
841 it's feasible for this array's length to exceed
842 <literal>FUNC_MAX_ARGS</literal> (which constrains only input
843 arguments). Even if that were not so,
844 <application>pg_dump</application> cannot assume that the server was
845 built with the same value of <literal>FUNC_MAX_ARGS</literal> that
846 it has. An overrun would lead to a memory clobber
847 inside <application>pg_dump</application>.
848 </para>
849
850 <para>
851 The <productname>PostgreSQL</productname> Project thanks
852 Masahiko Sawada
853 for reporting this problem.
854 (CVE-2026-19385)
855 </para>
856 </listitem>
857
858 <listitem>
859 <!--
860 Author: Tom Lane <[email protected]>
861 Branch: master [63cb15f40] 2026-08-10 06:37:48 -0700
862 Branch: REL_19_STABLE [8c48cd615] 2026-08-10 06:38:04 -0700
863 Branch: REL_18_STABLE [87c4b8219] 2026-08-10 06:38:11 -0700
864 Branch: REL_17_STABLE [2d78c34f8] 2026-08-10 06:38:17 -0700
865 Branch: REL_16_STABLE [477a6bdb0] 2026-08-10 06:38:23 -0700
866 Branch: REL_15_STABLE [cf4ae7c3b] 2026-08-10 06:38:29 -0700
867 Branch: REL_14_STABLE [d7fcfead3] 2026-08-10 06:38:35 -0700
868 -->
869 <para>
870 Harden <application>PL/Perl</application>
871 against <quote>tied</quote> Perl arrays and hashes (Tom Lane)
872 <ulink url="&commit_baseurl;87c4b8219">&sect;</ulink>
873 </para>
874
875 <para>
876 A tied object that doesn't behave like a regular one could lead to
877 memory overwrite, or to constructing a corrupt result array (which
878 would likely cause problems later).
879 </para>
880
881 <para>
882 The <productname>PostgreSQL</productname> Project thanks
883 Hcamael
884 for reporting this problem.
885 (CVE-2026-14670)
886 </para>
887 </listitem>
888
889 <listitem>
890 <!--
891 Author: Heikki Linnakangas <[email protected]>
892 Branch: master [776467301] 2026-08-10 06:37:49 -0700
893 Branch: REL_19_STABLE [a1c1727cb] 2026-08-10 06:38:05 -0700
894 Branch: REL_18_STABLE [028ee716a] 2026-08-10 06:38:11 -0700
895 Branch: REL_17_STABLE [b56cc7deb] 2026-08-10 06:38:18 -0700
896 Branch: REL_16_STABLE [8bbdc0540] 2026-08-10 06:38:24 -0700
897 Branch: REL_15_STABLE [1eb0d5380] 2026-08-10 06:38:30 -0700
898 Branch: REL_14_STABLE [aff9dac1c] 2026-08-10 06:38:35 -0700
899 -->
900 <para>
901 Fix integer overflows in memory-allocation calculations
902 in <application>PL/Perl</application>
903 and <application>PL/Tcl</application> (Heikki Linnakangas)
904 <ulink url="&commit_baseurl;028ee716a">&sect;</ulink>
905 </para>
906
907 <para>
908 This is the same type of problem as CVE-2026-6473, just in a
909 different part of the code, and is fixed in the same way.
910 </para>
911
912 <para>
913 The <productname>PostgreSQL</productname> Project thanks
914 the Tulya Project (Team Dhiutsa, Bitecope Technologies Private Ltd)
915 for reporting this problem.
916 (CVE-2026-14677)
917 </para>
918 </listitem>
919
920 <listitem>
921 <!--
922 Author: Noah Misch <[email protected]>
923 Branch: master [0fbf785b1] 2026-08-10 06:37:49 -0700
924 Branch: REL_19_STABLE [557cc7186] 2026-08-10 06:38:05 -0700
925 Branch: REL_18_STABLE [0a61fcde0] 2026-08-10 06:38:12 -0700
926 Branch: REL_17_STABLE [e41c72aff] 2026-08-10 06:38:18 -0700
927 Branch: REL_16_STABLE [2cc147318] 2026-08-10 06:38:24 -0700
928 Branch: REL_15_STABLE [e43e74756] 2026-08-10 06:38:30 -0700
929 Branch: REL_14_STABLE [39d792040] 2026-08-10 06:38:36 -0700
930 -->
931 <para>
932 Ensure that <filename>contrib/amcheck</filename> functions
933 restrict <varname>search_path</varname> before executing index
934 expressions (Noah Misch)
935 <ulink url="&commit_baseurl;0a61fcde0">&sect;</ulink>
936 </para>
937
938 <para>
939 Because amcheck will run such index expressions as the owner of
940 their tables, a caller could potentially
941 hijack <varname>search_path</varname>-dependent functions to run
942 arbitrary code as the table owner. By default this is not a
943 vulnerability because only superusers are allowed to call amcheck
944 functions; but if that privilege was granted out, it created a
945 larger hazard than the documentation suggests.
946 </para>
947
948 <para>
949 The <productname>PostgreSQL</productname> Project thanks
950 Yuelin Wang and Jacob Brazeal
951 for reporting this problem.
952 (CVE-2026-14673)
953 </para>
954 </listitem>
955
956 <listitem>
957 <!--
958 Author: Nathan Bossart <[email protected]>
959 Branch: master [918683d12] 2026-08-10 06:37:49 -0700
960 Branch: REL_19_STABLE [62c31b490] 2026-08-10 06:38:05 -0700
961 Branch: REL_18_STABLE [e88eb4e76] 2026-08-10 06:38:12 -0700
962 Branch: REL_17_STABLE [c4d51b627] 2026-08-10 06:38:19 -0700
963 Branch: REL_16_STABLE [61481aa0e] 2026-08-10 06:38:24 -0700
964 Branch: REL_15_STABLE [74916136f] 2026-08-10 06:38:30 -0700
965 Branch: REL_14_STABLE [9505175f2] 2026-08-10 06:38:36 -0700
966 -->
967 <para>
968 Fix integer overflows in <filename>contrib/fuzzystrmatch</filename>'s
969 <function>levenshtein()</function>
970 and <function>levenshtein_less_equal()</function> functions
971 (Nathan Bossart)
972 <ulink url="&commit_baseurl;e88eb4e76">&sect;</ulink>
973 </para>
974
975 <para>
976 Passing large cost values to these functions could cause integer
977 overflows, thereby producing nonsensical results, and even causing
978 out-of-bounds writes in some cases.
979 </para>
980
981 <para>
982 The <productname>PostgreSQL</productname> Project thanks
983 Ben Morris (in collaboration with Claude and Anthropic Research)
984 for reporting this problem.
985 (CVE-2026-15742)
986 </para>
987 </listitem>
988
989 <listitem>
990 <!--
991 Author: Álvaro Herrera <[email protected]>
992 Branch: master [1e2795dde] 2026-08-10 06:37:48 -0700
993 Branch: REL_19_STABLE [bb02eba53] 2026-08-10 06:38:04 -0700
994 Branch: REL_18_STABLE [8a31ffc2d] 2026-08-10 06:38:11 -0700
995 -->
996 <para>
997 Fix buffer overrun
998 in <filename>contrib/pg_stat_statements</filename> (Álvaro Herrera)
999 <ulink url="&commit_baseurl;8a31ffc2d">&sect;</ulink>
1000 </para>
1001
1002 <para>
1003 Query normalization didn't accurately account for the amount of
1004 space the normalized string would require.
1005 </para>
1006
1007 <para>
1008 The <productname>PostgreSQL</productname> Project thanks
1009 Sajeeb Lohani (with TrendAI Zero Day Initiative) and Yuelin Wang
1010 for reporting this problem.
1011 (CVE-2026-14676)
1012 </para>
1013 </listitem>
1014
1015 <listitem>
1016 <!--
1017 Author: Heikki Linnakangas <[email protected]>
1018 Branch: master [66c2dbb20] 2026-08-10 06:37:48 -0700
1019 Branch: REL_19_STABLE [aa7b5815e] 2026-08-10 06:38:04 -0700
1020 Branch: REL_18_STABLE [849019a50] 2026-08-10 06:38:11 -0700
1021 Branch: REL_17_STABLE [1af08af69] 2026-08-10 06:38:18 -0700
1022 Branch: REL_16_STABLE [24c88cd39] 2026-08-10 06:38:24 -0700
1023 Branch: REL_15_STABLE [c7c82a88c] 2026-08-10 06:38:29 -0700
1024 Branch: REL_14_STABLE [a74aa0854] 2026-08-10 06:38:35 -0700
1025 -->
1026 <para>
1027 Fix datatype error in <filename>contrib/pg_trgm</filename>'s GiST
1028 picksplit function (Heikki Linnakangas)
1029 <ulink url="&commit_baseurl;849019a50">&sect;</ulink>
1030 </para>
1031
1032 <para>
1033 This mistake resulted in reading past the end of the buffer,
1034 typically causing bad split decisions; but a crash could ensue
1035 if you're very unlucky.
1036 </para>
1037
1038 <para>
1039 The <productname>PostgreSQL</productname> Project thanks
1040 Mehmet D. Ince
1041 for reporting this problem.
1042 (CVE-2026-14678)
1043 </para>
1044 </listitem>
1045
1046 <listitem>
1047 <!--
1048 Author: Nathan Bossart <[email protected]>
1049 Branch: master Release: REL_19_BR [1fbe2066d] 2026-06-05 12:08:05 -0500
1050 Branch: REL_18_STABLE [79a506228] 2026-06-05 12:08:05 -0500
1051 Branch: REL_17_STABLE [66a5146dc] 2026-06-05 12:08:05 -0500
1052 Branch: REL_16_STABLE [a572dd213] 2026-06-05 12:08:05 -0500
1053 Branch: REL_15_STABLE [b7b513d9a] 2026-06-05 12:08:05 -0500
1054 Branch: REL_14_STABLE [5b72d0279] 2026-06-05 12:08:05 -0500
1055 -->
1056 <para>
1057 Remove the plan cache in <filename>contrib/refint</filename>
1058 (Ayush Tiwari)
1059 <ulink url="&commit_baseurl;79a506228">&sect;</ulink>
1060 </para>
1061
1062 <para>
1063 This caching behavior has several serious bugs, notably that
1064 <function>check_foreign_key()</function> embeds the new key values
1065 in its cascade-UPDATE queries, so a cached plan reuses the
1066 originally-needed values rather than the key values that should be
1067 used. The simplest solution is to remove it.
1068 </para>
1069
1070 <para>
1071 The <productname>PostgreSQL</productname> Project thanks
1072 Hcamael
1073 for reporting this problem.
1074 (CVE-2026-14671)
1075 </para>
1076 </listitem>
1077
1078 <listitem>
1079 <!--
1080 Author: Tomas Vondra <[email protected]>
1081 Branch: master [1232f7a08] 2026-07-30 14:59:12 +0200
1082 Branch: REL_19_STABLE [5707d7517] 2026-07-30 14:59:30 +0200
1083 Branch: REL_18_STABLE [d4420a972] 2026-07-30 14:59:39 +0200
1084 -->
1085 <para>
1086 Ensure that parallel GIN index builds update the table's
1087 <structname>pg_class</structname>.<structfield>reltuples</structfield>
1088 value correctly (Jan Nidzwetzki, Tomas Vondra)
1089 <ulink url="&commit_baseurl;d4420a972">&sect;</ulink>
1090 </para>
1091
1092 <para>
1093 A parallel worker could report an uninitialized value for the
1094 number of rows it processed, leading to a bogus value
1095 for <structfield>reltuples</structfield>, even Infinity or NaN.
1096 Such values could lead to subsequent autovacuum and autoanalyze
1097 operations never deciding that the table needs to be processed.
1098 If so, the situation will not self-heal. A manual
1099 <command>ANALYZE</command> command, or creation of another index,
1100 will be needed to reset <structfield>reltuples</structfield> to
1101 the correct value. If you have any tables with GIN indexes, it's
1102 recommended to check to see if
1103 their <structfield>reltuples</structfield> entries look sane.
1104 A query such as this may be helpful:
1105 <programlisting>
1106 SELECT DISTINCT t.oid::regclass, t.reltuples
1107 FROM pg_class t
1108 JOIN pg_index i ON t.oid = i.indrelid
1109 JOIN pg_class ic ON i.indexrelid = ic.oid
1110 WHERE t.relhasindex AND ic.relam = 2742;
1111 </programlisting>
1112 </para>
1113 </listitem>
1114
1115 <listitem>
1116 <!--
1117 Author: Etsuro Fujita <[email protected]>
1118 Branch: master [f57df2068] 2026-08-07 17:30:00 +0900
1119 Branch: REL_19_STABLE [7d74b2644] 2026-08-07 17:30:01 +0900
1120 Branch: REL_18_STABLE [4ea497a92] 2026-08-07 17:30:02 +0900
1121 Branch: REL_17_STABLE [3704870b2] 2026-08-07 17:30:03 +0900
1122 Branch: REL_16_STABLE [894da35b3] 2026-08-07 17:30:04 +0900
1123 Branch: REL_15_STABLE [7213cbfa0] 2026-08-07 17:30:05 +0900
1124 Branch: REL_14_STABLE [cec48686a] 2026-08-07 17:30:06 +0900
1125 -->
1126 <para>
1127 Fix mis-handling of asynchronous reads when rescanning an
1128 asynchronous Append plan node (Alexander Korotkov, Gleb Kashkin,
1129 Etsuro Fujita)
1130 <ulink url="&commit_baseurl;4ea497a92">&sect;</ulink>
1131 </para>
1132
1133 <para>
1134 When an upper plan node rescans an Append before having read the
1135 entire Append output, we need to discard any in-flight requests sent
1136 to external servers (by <filename>postgres_fdw</filename> for
1137 example). This was not done correctly in cases where a subplan has
1138 parameter changes or is discarded by partition pruning in the next
1139 scan. The outcome could be incorrect query results, an infinite
1140 loop, or an assertion failure.
1141 </para>
1142 </listitem>
1143
1144 <listitem>
1145 <!--
1146 Author: David Rowley <[email protected]>
1147 Branch: master [709dfd27f] 2026-07-31 15:36:31 +1200
1148 Branch: REL_19_STABLE [f9282a650] 2026-07-31 15:37:12 +1200
1149 Branch: REL_18_STABLE [02e69be47] 2026-07-31 15:37:42 +1200
1150 Branch: REL_17_STABLE [31f2acde5] 2026-07-31 15:38:10 +1200
1151 Branch: REL_16_STABLE [9a0cd8e73] 2026-07-31 15:38:34 +1200
1152 Branch: REL_15_STABLE [5190732c9] 2026-07-31 15:39:01 +1200
1153 Branch: REL_14_STABLE [6098f35f4] 2026-07-31 15:39:21 +1200
1154 -->
1155 <para>
1156 Fix error in partition pruning for RANGE-partitioned tables
1157 (David Rowley)
1158 <ulink url="&commit_baseurl;02e69be47">&sect;</ulink>
1159 </para>
1160
1161 <para>
1162 In some cases the DEFAULT partition would be skipped when it should
1163 not be, which could lead to rows missing from query results.
1164 </para>
1165 </listitem>
1166
1167 <listitem>
1168 <!--
1169 Author: Amit Langote <[email protected]>
1170 Branch: master Release: REL_19_BR [b43f8aa4c] 2026-06-24 08:59:22 +0900
1171 Branch: REL_18_STABLE [1ef917e3a] 2026-06-23 21:08:50 +0900
1172 Branch: REL_18_STABLE [bba4e095d] 2026-06-25 12:15:02 +0900
1173 -->
1174 <para>
1175 Correctly update foreign-data-wrapper state in a ModifyTable plan
1176 node after pruning result relations (Ayush Tiwari, Rafia Sabih)
1177 <ulink url="&commit_baseurl;1ef917e3a">&sect;</ulink>
1178 <ulink url="&commit_baseurl;bba4e095d">&sect;</ulink>
1179 </para>
1180
1181 <para>
1182 Previously, if run-time partition pruning determined that some
1183 partitions of a partitioned target table need not be scanned
1184 and the table had any foreign-table partitions, a crash
1185 or erroneous behavior was likely.
1186 </para>
1187 </listitem>
1188
1189 <listitem>
1190 <!--
1191 Author: Dean Rasheed <[email protected]>
1192 Branch: master [8e0c25275] 2026-07-08 20:46:25 +0100
1193 Branch: REL_19_STABLE [7048e50f8] 2026-07-08 20:46:25 +0100
1194 Branch: REL_18_STABLE [4908225be] 2026-07-08 20:46:26 +0100
1195 -->
1196 <para>
1197 Fix missed concurrent update in <command>UPDATE</command>
1198 with <literal>RETURNING OLD</literal> on a table that has
1199 a <literal>BEFORE UPDATE</literal> trigger (Dean Rasheed)
1200 <ulink url="&commit_baseurl;4908225be">&sect;</ulink>
1201 </para>
1202
1203 <para>
1204 If the target row was concurrently updated, then at isolation
1205 level <literal>READ COMMITTED</literal> any <literal>OLD</literal>
1206 values in <literal>RETURNING</literal> should reflect the updated
1207 row. But stale values were returned if there was a trigger
1208 (although the trigger itself, and the final output row, saw the
1209 correct values).
1210 </para>
1211 </listitem>
1212
1213 <listitem>
1214 <!--
1215 Author: David Rowley <[email protected]>
1216 Branch: master [60826a352] 2026-07-31 23:23:21 +1200
1217 Branch: REL_19_STABLE [a71a348ed] 2026-07-31 23:24:23 +1200
1218 Branch: REL_18_STABLE [f70acc8a2] 2026-07-31 23:24:46 +1200
1219 -->
1220 <para>
1221 Fix hash join performance issue when there are multiple join keys
1222 and many NULL values (David Rowley)
1223 <ulink url="&commit_baseurl;f70acc8a2">&sect;</ulink>
1224 </para>
1225
1226 <para>
1227 Null-keyed tuples should not get inserted into the hash table, since
1228 they will never match any other tuples. The code got this wrong if
1229 the null was in a non-last join column, bloating the hash table
1230 quite a lot if many inputs contain nulls.
1231 </para>
1232 </listitem>
1233
1234 <listitem>
1235 <!--
1236 Author: Dean Rasheed <[email protected]>
1237 Branch: master Release: REL_19_BR [79c65b9d9] 2026-06-11 12:08:47 +0100
1238 Branch: REL_18_STABLE [9108fed3e] 2026-06-11 12:08:48 +0100
1239 -->
1240 <para>
1241 Fix parsing of
1242 parenthesized <literal>OLD</literal>/<literal>NEW</literal>
1243 in <literal>RETURNING</literal> expressions (Marko Grujic)
1244 <ulink url="&commit_baseurl;9108fed3e">&sect;</ulink>
1245 </para>
1246
1247 <para>
1248 Expressions such as <literal>(old).colname</literal>
1249 and <literal>(old).*</literal> were mis-handled, effectively
1250 converting them to <literal>NEW</literal> references.
1251 </para>
1252 </listitem>
1253
1254 <listitem>
1255 <!--
1256 Author: Tom Lane <[email protected]>
1257 Branch: master [239eabda4] 2026-07-28 16:09:03 -0400
1258 Branch: REL_19_STABLE [9740c68ff] 2026-07-28 16:09:03 -0400
1259 Branch: REL_18_STABLE [277122036] 2026-07-28 16:09:03 -0400
1260 Branch: REL_17_STABLE [26d6b7dc9] 2026-07-28 16:09:04 -0400
1261 Branch: REL_16_STABLE [6fcee189b] 2026-07-28 16:09:04 -0400
1262 Branch: REL_15_STABLE [53470ffba] 2026-07-28 16:09:04 -0400
1263 Branch: REL_14_STABLE [13b627a3e] 2026-07-28 16:09:04 -0400
1264 -->
1265 <para>
1266 Fix planner's nullability and strictness checks
1267 for <literal><replaceable>value</replaceable> IN
1268 (<replaceable>array</replaceable>)</literal> expressions
1269 (Ayush Tiwari)
1270 <ulink url="&commit_baseurl;277122036">&sect;</ulink>
1271 </para>
1272
1273 <para>
1274 These checks should only succeed if the array operand is known to be
1275 non-empty, but that consideration was missed, allowing optimizations
1276 to be applied that should not be. This could result in wrong query
1277 answers if the array actually was empty.
1278 </para>
1279 </listitem>
1280
1281 <listitem>
1282 <!--
1283 Author: Tom Lane <[email protected]>
1284 Branch: master [1df9e8d96] 2026-07-18 14:09:10 -0400
1285 Branch: REL_19_STABLE [8bc479627] 2026-07-18 14:09:10 -0400
1286 Branch: REL_18_STABLE [21f5e659e] 2026-07-18 14:09:10 -0400
1287 Branch: REL_17_STABLE [cdcec567d] 2026-07-18 14:09:10 -0400
1288 Branch: REL_16_STABLE [3e1fe25e6] 2026-07-18 14:09:10 -0400
1289 Author: Richard Guo <[email protected]>
1290 Branch: master [0da71d90d] 2026-07-20 12:13:11 +0900
1291 Branch: REL_19_STABLE [72457f1df] 2026-07-20 12:15:09 +0900
1292 Branch: REL_18_STABLE [9e40d07e1] 2026-07-20 12:15:57 +0900
1293 Branch: REL_17_STABLE [b308eb366] 2026-07-20 12:16:58 +0900
1294 Branch: REL_16_STABLE [d610d8e8b] 2026-07-20 12:17:40 +0900
1295 -->
1296 <para>
1297 Fix incorrect join removal logic (Matheus Alcantara, Richard Guo)
1298 <ulink url="&commit_baseurl;21f5e659e">&sect;</ulink>
1299 <ulink url="&commit_baseurl;9e40d07e1">&sect;</ulink>
1300 </para>
1301
1302 <para>
1303 In edge cases, it was possible for a constant output value coming
1304 from within the nullable side of an outer join to not be replaced by
1305 NULL when it should be.
1306 </para>
1307 </listitem>
1308
1309 <listitem>
1310 <!--
1311 Author: Richard Guo <[email protected]>
1312 Branch: master Release: REL_19_BR [9a60f295b] 2026-06-22 10:40:40 +0900
1313 Branch: REL_18_STABLE [e02526795] 2026-06-22 10:43:01 +0900
1314 Branch: master [d68576bcf] 2026-07-15 09:20:35 +0900
1315 Branch: REL_19_STABLE [aae47813a] 2026-07-15 09:21:44 +0900
1316 Branch: REL_18_STABLE [18105e6db] 2026-07-15 09:22:58 +0900
1317 -->
1318 <para>
1319 Clean up PlaceHolderVars more thoroughly during join removal
1320 (Richard Guo, Arne Roland)
1321 <ulink url="&commit_baseurl;e02526795">&sect;</ulink>
1322 <ulink url="&commit_baseurl;18105e6db">&sect;</ulink>
1323 </para>
1324
1325 <para>
1326 This fix corrects various edge cases that could trip assertions or
1327 result in incorrect plans.
1328 </para>
1329 </listitem>
1330
1331 <listitem>
1332 <!--
1333 Author: Tom Lane <[email protected]>
1334 Branch: master Release: REL_19_BR [06e94eccf] 2026-06-08 11:48:16 -0400
1335 Branch: REL_18_STABLE [11aed8d19] 2026-06-08 11:48:17 -0400
1336 Branch: REL_17_STABLE [19152e3c2] 2026-06-08 11:48:17 -0400
1337 Branch: REL_16_STABLE [cf2bfe073] 2026-06-08 11:48:17 -0400
1338 Branch: REL_15_STABLE [caebac5f1] 2026-06-08 11:48:18 -0400
1339 Branch: REL_14_STABLE [64778fac7] 2026-06-08 11:48:18 -0400
1340 -->
1341 <para>
1342 Add missed checks for hashability of equality comparisons on
1343 container datatypes (arrays, composites, ranges) (Andrei Lepikhov,
1344 Tom Lane)
1345 <ulink url="&commit_baseurl;11aed8d19">&sect;</ulink>
1346 </para>
1347
1348 <para>
1349 The planner must verify hashability of the container's component
1350 type(s) before deciding it can use a hash-based plan type. This
1351 step was missed in some places, leading to <quote>could not identify
1352 a hash function</quote> failures at execution.
1353 </para>
1354 </listitem>
1355
1356 <listitem>
1357 <!--
1358 Author: Richard Guo <[email protected]>
1359 Branch: master [44fb59fc6] 2026-07-06 16:13:14 +0900
1360 Branch: REL_19_STABLE [98d5d7ee6] 2026-07-06 16:14:13 +0900
1361 Branch: REL_18_STABLE [fe5d62951] 2026-07-06 16:15:45 +0900
1362 -->
1363 <para>
1364 Avoid pushing <literal>WHERE</literal> clauses down past a grouping
1365 step that has a different equivalence rule (Richard Guo)
1366 <ulink url="&commit_baseurl;fe5d62951">&sect;</ulink>
1367 </para>
1368
1369 <para>
1370 A test on a grouping column that is grouped by a nondeterministic
1371 collation is safe to push down only if it is a comparison using that
1372 same collation. Otherwise it might filter some rows the grouping
1373 would have merged.
1374 </para>
1375 </listitem>
1376
1377 <listitem>
1378 <!--
1379 Author: David Rowley <[email protected]>
1380 Branch: master [d007800f0] 2026-07-07 23:57:45 +1200
1381 Branch: REL_19_STABLE [fcd58c6d9] 2026-07-07 23:58:29 +1200
1382 Branch: REL_18_STABLE [cf184ec77] 2026-07-07 23:59:08 +1200
1383 Branch: REL_17_STABLE [be63b285e] 2026-07-07 23:59:33 +1200
1384 Branch: REL_16_STABLE [a85732162] 2026-07-08 00:00:03 +1200
1385 Branch: REL_15_STABLE [842e34efa] 2026-07-08 00:00:34 +1200
1386 -->
1387 <para>
1388 Fix mis-optimization of <function>COUNT</function> window functions
1389 that have an <literal>EXCLUDE</literal> clause or
1390 lack <literal>ORDER BY</literal> (Chengpeng Yan, David Rowley)
1391 <ulink url="&commit_baseurl;cf184ec77">&sect;</ulink>
1392 </para>
1393
1394 <para>
1395 These window functions were treated as monotonic when they should
1396 not be, allowing wrong answers to be computed.
1397 </para>
1398 </listitem>
1399
1400 <listitem>
1401 <!--
1402 Author: Tom Lane <[email protected]>
1403 Branch: master Release: REL_19_BR [b574fec00] 2026-06-28 12:31:29 -0400
1404 Branch: REL_18_STABLE [5fd1c3f28] 2026-06-28 12:31:29 -0400
1405 -->
1406 <para>
1407 Avoid <quote>cache lookup failed for collation 0</quote> error when
1408 planner looks up statistics for a column of type <type>"char"</type>
1409 (Feng Wu)
1410 <ulink url="&commit_baseurl;5fd1c3f28">&sect;</ulink>
1411 </para>
1412 </listitem>
1413
1414 <listitem>
1415 <!--
1416 Author: Álvaro Herrera <[email protected]>
1417 Branch: master [fef160d8b] 2026-08-04 09:06:46 +0200
1418 Branch: REL_19_STABLE [ce6e434ce] 2026-08-04 09:06:46 +0200
1419 Branch: REL_18_STABLE [c374f2807] 2026-08-04 09:06:46 +0200
1420 Branch: REL_17_STABLE [18006c1bd] 2026-08-04 09:06:46 +0200
1421 Branch: REL_16_STABLE [34785a0d5] 2026-08-04 09:06:46 +0200
1422 Branch: REL_15_STABLE [785289de0] 2026-08-04 09:06:46 +0200
1423 Branch: REL_14_STABLE [cad17745e] 2026-08-04 09:06:46 +0200
1424 -->
1425 <para>
1426 Fix <command>ALTER COLUMN ... DROP EXPRESSION</command> to work when
1427 there are multiple levels of partitions (Alberto Piai)
1428 <ulink url="&commit_baseurl;c374f2807">&sect;</ulink>
1429 </para>
1430 </listitem>
1431
1432 <listitem>
1433 <!--
1434 Author: Álvaro Herrera <[email protected]>
1435 Branch: master [d049a31a4] 2026-07-20 17:21:20 +0200
1436 Branch: REL_19_STABLE [2b2c2492c] 2026-07-20 17:21:20 +0200
1437 Branch: REL_18_STABLE [19e3aa704] 2026-07-20 17:21:20 +0200
1438 Branch: REL_17_STABLE [1d6c654c8] 2026-07-20 17:21:20 +0200
1439 -->
1440 <para>
1441 Fix attaching partitions of indexes that are exclusion constraints
1442 (Japin Li)
1443 <ulink url="&commit_baseurl;19e3aa704">&sect;</ulink>
1444 </para>
1445
1446 <para>
1447 Notably, this oversight broke dump/restore of partitioned exclusion
1448 constraints.
1449 </para>
1450 </listitem>
1451
1452 <listitem>
1453 <!--
1454 Author: Fujii Masao <[email protected]>
1455 Branch: master Release: REL_19_BR [d8b5d87e5] 2026-05-22 23:59:04 +0900
1456 Branch: REL_18_STABLE [41247cdf6] 2026-05-23 00:01:24 +0900
1457 -->
1458 <para>
1459 Prevent setting <literal>NO INHERIT</literal> on
1460 partitioned <literal>NOT NULL</literal> constraints
1461 via <command>ALTER CONSTRAINT</command> (Andreas Karlsson)
1462 <ulink url="&commit_baseurl;41247cdf6">&sect;</ulink>
1463 </para>
1464
1465 <para>
1466 <literal>NOT NULL</literal> constraints on partitioned tables are
1467 supposed to be inherited by all partitions, and therefore must not
1468 be marked <literal>NO INHERIT</literal>. This rule was correctly
1469 enforced by constraint creation, but not by <command>ALTER TABLE
1470 ... ALTER CONSTRAINT</command>.
1471 </para>
1472 </listitem>
1473
1474 <listitem>
1475 <!--
1476 Author: Tom Lane <[email protected]>
1477 Branch: master [a8c2547ea] 2026-07-04 11:34:26 -0400
1478 Branch: REL_19_STABLE [80c7f5467] 2026-07-04 11:34:26 -0400
1479 Branch: REL_18_STABLE [a7f7958ab] 2026-07-04 11:34:26 -0400
1480 Branch: REL_17_STABLE [e99fb3262] 2026-07-04 11:34:26 -0400
1481 Branch: REL_16_STABLE [a69503fb1] 2026-07-04 11:34:26 -0400
1482 Branch: REL_15_STABLE [eada45dd8] 2026-07-04 11:34:26 -0400
1483 Branch: REL_14_STABLE [1b17a6e3c] 2026-07-04 11:34:26 -0400
1484 -->
1485 <para>
1486 Disallow renaming a rule to <literal>_RETURN</literal> (Tom Lane)
1487 <ulink url="&commit_baseurl;a7f7958ab">&sect;</ulink>
1488 </para>
1489
1490 <para>
1491 That name is reserved for a view's <literal>ON SELECT</literal>
1492 rule, but <command>ALTER RULE</command> allowed renaming other rules
1493 to <literal>_RETURN</literal>, causing trouble later.
1494 </para>
1495 </listitem>
1496
1497 <listitem>
1498 <!--
1499 Author: Jeff Davis <[email protected]>
1500 Branch: master [b48caa7df] 2026-08-03 12:21:05 -0700
1501 Branch: REL_19_STABLE [9eccdae22] 2026-08-03 12:25:15 -0700
1502 Branch: REL_18_STABLE [a0daa0b41] 2026-08-03 12:25:31 -0700
1503 Branch: REL_17_STABLE [25e54cec7] 2026-08-03 12:25:41 -0700
1504 Branch: REL_16_STABLE [e61d44fde] 2026-08-03 12:25:49 -0700
1505 -->
1506 <para>
1507 Fix missing lock release for role membership grants in <command>DROP
1508 OWNED BY</command> (Jeff Davis)
1509 <ulink url="&commit_baseurl;a0daa0b41">&sect;</ulink>
1510 </para>
1511
1512 <para>
1513 This oversight resulted in a warning message, followed by retaining
1514 a lock on the membership grant until the end of the transaction.
1515 </para>
1516 </listitem>
1517
1518 <listitem>
1519 <!--
1520 Author: Richard Guo <[email protected]>
1521 Branch: master [96ab9a990] 2026-07-08 08:46:43 +0900
1522 Branch: REL_19_STABLE [eaa561fb6] 2026-07-08 08:48:29 +0900
1523 Branch: REL_18_STABLE [45364e496] 2026-07-08 08:49:12 +0900
1524 Branch: REL_17_STABLE [dcda1f07d] 2026-07-08 08:50:14 +0900
1525 Branch: REL_16_STABLE [485527190] 2026-07-08 08:51:09 +0900
1526 -->
1527 <para>
1528 Fix failure of <command>EXPLAIN</command> when
1529 deparsing <literal>SQL/JSON</literal> aggregates (Richard Guo)
1530 <ulink url="&commit_baseurl;45364e496">&sect;</ulink>
1531 </para>
1532
1533 <para>
1534 Some plan structures resulted in <quote>invalid
1535 JsonConstructorExpr underlying node type</quote> errors.
1536 </para>
1537 </listitem>
1538
1539 <listitem>
1540 <!--
1541 Author: Michael Paquier <[email protected]>
1542 Branch: master [74276e685] 2026-07-28 08:33:23 +0900
1543 Branch: REL_19_STABLE [9f6fb1191] 2026-07-28 08:35:09 +0900
1544 Branch: REL_18_STABLE [e4527519b] 2026-07-28 08:35:12 +0900
1545 Branch: REL_17_STABLE [28269fed6] 2026-07-28 08:35:14 +0900
1546 Branch: REL_16_STABLE [ac222bea5] 2026-07-28 08:35:17 +0900
1547 Branch: REL_15_STABLE [5b3712e31] 2026-07-28 08:35:19 +0900
1548 Branch: REL_14_STABLE [55adef7ab] 2026-07-28 08:35:21 +0900
1549 -->
1550 <para>
1551 Fix use of <command>REINDEX CONCURRENTLY</command> with
1552 a deferred uniqueness constraint (Nitin Motiani)
1553 <ulink url="&commit_baseurl;e4527519b">&sect;</ulink>
1554 </para>
1555
1556 <para>
1557 The transient index copy created during <command>REINDEX
1558 CONCURRENTLY</command> was incorrectly marked as enforcing immediate
1559 uniqueness, causing spurious reports of constraint violation.
1560 </para>
1561 </listitem>
1562
1563 <listitem>
1564 <!--
1565 Author: Tom Lane <[email protected]>
1566 Branch: master [d6ffcae32] 2026-07-06 14:35:21 -0400
1567 Branch: REL_19_STABLE [99775b388] 2026-07-06 14:35:21 -0400
1568 Branch: REL_18_STABLE [a99bd8d58] 2026-07-06 14:35:21 -0400
1569 Branch: master [42b7ff3aa] 2026-07-06 14:47:58 -0400
1570 Branch: REL_19_STABLE [54d5947ef] 2026-07-06 14:47:58 -0400
1571 Branch: REL_18_STABLE [51652c42d] 2026-07-06 14:47:58 -0400
1572 -->
1573 <para>
1574 Fix <literal>LIKE</literal> matching with nondeterministic
1575 collations and backslashes (Nitin Motiani, Tom Lane)
1576 <ulink url="&commit_baseurl;a99bd8d58">&sect;</ulink>
1577 <ulink url="&commit_baseurl;51652c42d">&sect;</ulink>
1578 </para>
1579
1580 <para>
1581 When using a nondeterministic collation, <literal>LIKE</literal>
1582 mishandled an escaped backslash (<literal>\\</literal>), treating it
1583 as effectively not there. It also did the wrong thing with a
1584 leading backslash preceding an ordinary character; in that case the
1585 backslash should be effectively ignored, but it caused the ordinary
1586 character to be matched exactly rather than allowing the
1587 nondeterministic collation to decide if there's a match.
1588 </para>
1589 </listitem>
1590
1591 <listitem>
1592 <!--
1593 Author: Tom Lane <[email protected]>
1594 Branch: master [2d7808e6f] 2026-07-06 13:06:24 -0400
1595 Branch: REL_19_STABLE [67cf73ddb] 2026-07-06 13:06:25 -0400
1596 Branch: REL_18_STABLE [d0bb49e61] 2026-07-06 13:06:25 -0400
1597 -->
1598 <para>
1599 Fix <literal>LIKE</literal>/regex optimization for indexscan with
1600 exact-match pattern (Jelte Fennema-Nio)
1601 <ulink url="&commit_baseurl;d0bb49e61">&sect;</ulink>
1602 </para>
1603
1604 <para>
1605 Refactoring for <literal>LIKE</literal> with non-deterministic
1606 collations accidentally broke the optimization for converting
1607 a <literal>LIKE</literal> or regex exact-match pattern to an
1608 equality index condition when the index collation doesn't match
1609 the expression collation. Among other things, that
1610 made <application>psql</application>'s
1611 <literal>\d <replaceable>tablename</replaceable></literal>
1612 command much slower.
1613 </para>
1614 </listitem>
1615
1616 <listitem>
1617 <!--
1618 Author: Álvaro Herrera <[email protected]>
1619 Branch: master [fd2b89854] 2026-08-05 11:40:39 +0200
1620 Branch: REL_19_STABLE [55ea76426] 2026-08-05 11:40:39 +0200
1621 Branch: REL_18_STABLE [011384ba4] 2026-08-05 11:40:39 +0200
1622 Branch: REL_17_STABLE [8acfaa12a] 2026-08-05 11:40:39 +0200
1623 Branch: REL_16_STABLE [b594efe52] 2026-08-05 11:40:39 +0200
1624 Branch: REL_15_STABLE [0de744cd5] 2026-08-05 11:40:39 +0200
1625 Branch: REL_14_STABLE [49a712f32] 2026-08-05 11:40:39 +0200
1626 Author: Heikki Linnakangas <[email protected]>
1627 Branch: REL_18_STABLE [5f003855e] 2026-08-11 21:24:28 +0300
1628 -->
1629 <para>
1630 Fix matching of localized month/day names
1631 in <function>to_date()</function> (Heikki Linnakangas)
1632 <ulink url="&commit_baseurl;011384ba4">&sect;</ulink>
1633 <ulink url="&commit_baseurl;5f003855e">&sect;</ulink>
1634 </para>
1635
1636 <para>
1637 The matching logic misbehaved in cases where case-folding changes
1638 the byte length of the string.
1639 </para>
1640 </listitem>
1641
1642 <listitem>
1643 <!--
1644 Author: Jeff Davis <[email protected]>
1645 Branch: master [368693689] 2026-07-07 14:53:41 -0700
1646 Branch: REL_19_STABLE [28d498e28] 2026-07-07 14:29:21 -0700
1647 Branch: REL_18_STABLE [66ec24276] 2026-07-07 15:04:31 -0700
1648 -->
1649 <para>
1650 Correct case-folding rules for Greek final sigma (Jeff Davis)
1651 <ulink url="&commit_baseurl;66ec24276">&sect;</ulink>
1652 </para>
1653
1654 <para>
1655 If the string is preceded only by Case Ignorable characters, don't
1656 consider it to be a final sigma. This only affects the
1657 built-in <literal>pg_unicode_fast</literal> locale.
1658 </para>
1659 </listitem>
1660
1661 <listitem>
1662 <!--
1663 Author: Michael Paquier <[email protected]>
1664 Branch: master Release: REL_19_BR [f2ff15e4c] 2026-06-05 07:50:08 +0900
1665 Branch: REL_18_STABLE [273fe9485] 2026-06-05 07:50:12 +0900
1666 Branch: REL_17_STABLE [0c9cbbfb5] 2026-06-05 07:50:13 +0900
1667 Branch: REL_16_STABLE [82116023e] 2026-06-05 07:50:15 +0900
1668 Branch: REL_15_STABLE [c391375ba] 2026-06-05 07:50:16 +0900
1669 Branch: REL_14_STABLE [8bb935d61] 2026-06-05 07:50:18 +0900
1670 -->
1671 <para>
1672 Fix incorrect NFC recomposition for Hangul U+11A7 (TBASE)
1673 (Diego Frias, Michael Paquier)
1674 <ulink url="&commit_baseurl;273fe9485">&sect;</ulink>
1675 </para>
1676
1677 <para>
1678 This character was treated as a valid T syllable, which it is not,
1679 and hence silently swallowed during normalization.
1680 </para>
1681 </listitem>
1682
1683 <listitem>
1684 <!--
1685 Author: Jeff Davis <[email protected]>
1686 Branch: master Release: REL_19_BR [9234e3337] 2026-06-08 11:47:53 -0700
1687 Branch: REL_18_STABLE [89e648498] 2026-06-08 11:47:40 -0700
1688 Branch: REL_17_STABLE [3805641cb] 2026-06-08 11:48:27 -0700
1689 Branch: REL_16_STABLE [b32df590c] 2026-06-08 11:48:48 -0700
1690 Branch: REL_15_STABLE [a7e0e42a2] 2026-06-08 11:49:11 -0700
1691 Branch: REL_14_STABLE [1e0458172] 2026-06-08 11:49:27 -0700
1692 -->
1693 <para>
1694 Avoid possible truncation of output lexemes in case-insensitive
1695 <literal>synonym</literal> dictionaries (Jeff Davis)
1696 <ulink url="&commit_baseurl;89e648498">&sect;</ulink>
1697 </para>
1698
1699 <para>
1700 If folding to lower case increased the byte length of a lexeme, it
1701 was incorrectly truncated to its original byte length when emitted.
1702 </para>
1703 </listitem>
1704
1705 <listitem>
1706 <!--
1707 Author: Jeff Davis <[email protected]>
1708 Branch: master [21ffc271d] 2026-07-07 13:34:55 -0700
1709 Branch: REL_19_STABLE [05da336dd] 2026-07-07 13:35:07 -0700
1710 Branch: REL_18_STABLE [9021c8f3c] 2026-07-07 13:35:15 -0700
1711 Branch: REL_17_STABLE [5e78ebca5] 2026-07-07 13:35:23 -0700
1712 -->
1713 <para>
1714 Defend against truncated UTF-8 characters in case-conversion logic
1715 (Jeff Davis)
1716 <ulink url="&commit_baseurl;9021c8f3c">&sect;</ulink>
1717 </para>
1718 </listitem>
1719
1720 <listitem>
1721 <!--
1722 Author: Michael Paquier <[email protected]>
1723 Branch: master Release: REL_19_BR [273a3c776] 2026-06-03 12:47:22 +0900
1724 Branch: REL_18_STABLE [b3f13c032] 2026-06-03 12:47:26 +0900
1725 Branch: REL_17_STABLE [203e238bb] 2026-06-03 12:47:28 +0900
1726 Branch: REL_16_STABLE [8b5580a05] 2026-06-03 12:47:30 +0900
1727 Branch: REL_15_STABLE [259b627d5] 2026-06-03 12:47:32 +0900
1728 Branch: REL_14_STABLE [74d3482f4] 2026-06-03 12:47:34 +0900
1729 -->
1730 <para>
1731 Fix typo in <function>hash_record_extended()</function> (Man Zeng)
1732 <ulink url="&commit_baseurl;b3f13c032">&sect;</ulink>
1733 </para>
1734
1735 <para>
1736 The code failed to initialize the second isnull argument passed to
1737 FunctionCallInvoke(). This is harmless for existing in-core
1738 extended hash support functions, which will not examine that value.
1739 However, extension-provided hash functions could be affected if they
1740 inspect <literal>PG_ARGISNULL(1)</literal>.
1741 </para>
1742 </listitem>
1743
1744 <listitem>
1745 <!--
1746 Author: Masahiko Sawada <[email protected]>
1747 Branch: master [63e7a0d2c] 2026-07-28 10:39:36 -0700
1748 Branch: REL_19_STABLE [28c995948] 2026-07-28 10:39:40 -0700
1749 Branch: REL_18_STABLE [73d63d1c1] 2026-07-28 10:39:43 -0700
1750 Branch: REL_17_STABLE [dcbc96685] 2026-07-28 10:39:47 -0700
1751 Branch: REL_16_STABLE [6c760f6b6] 2026-07-28 10:39:50 -0700
1752 -->
1753 <para>
1754 Fix <function>pg_get_publication_tables()</function> to not fail if
1755 a publishable table is dropped concurrently (Bharath Rupireddy)
1756 <ulink url="&commit_baseurl;73d63d1c1">&sect;</ulink>
1757 </para>
1758 </listitem>
1759
1760 <listitem>
1761 <!--
1762 Author: Robert Haas <[email protected]>
1763 Branch: master [e8914ec22] 2026-07-06 12:51:29 -0400
1764 Branch: REL_19_STABLE [2ddc45662] 2026-07-06 12:31:42 -0400
1765 Branch: REL_18_STABLE [0c06ebf12] 2026-07-06 12:24:03 -0400
1766 Branch: REL_17_STABLE [52af6fef4] 2026-07-06 12:24:10 -0400
1767 Branch: REL_16_STABLE [6de480156] 2026-07-06 12:24:16 -0400
1768 Branch: REL_15_STABLE [d39b9eed0] 2026-07-06 12:24:23 -0400
1769 Branch: REL_14_STABLE [0115650de] 2026-07-06 12:24:28 -0400
1770 -->
1771 <para>
1772 Prevent <function>satisfies_hash_partition()</function> from
1773 crashing with <literal>VARIADIC NULL</literal> (Robert Haas)
1774 <ulink url="&commit_baseurl;0c06ebf12">&sect;</ulink>
1775 </para>
1776 </listitem>
1777
1778 <listitem>
1779 <!--
1780 Author: Tom Lane <[email protected]>
1781 Branch: master Release: REL_19_BR [ce6bf3cd1] 2026-06-04 12:24:51 -0400
1782 Branch: REL_18_STABLE [c5194139c] 2026-06-04 12:24:51 -0400
1783 Branch: REL_17_STABLE [0626fbfeb] 2026-06-04 12:24:51 -0400
1784 Branch: REL_16_STABLE [ed5ca5828] 2026-06-04 12:24:51 -0400
1785 Branch: REL_15_STABLE [b3a86eb6d] 2026-06-04 12:24:51 -0400
1786 Branch: REL_14_STABLE [262cc4df2] 2026-06-04 12:24:51 -0400
1787 -->
1788 <para>
1789 Report invalid-weight errors more cleanly and consistently
1790 in <function>tsvector_filter()</function> and allied functions
1791 (Ewan Young)
1792 <ulink url="&commit_baseurl;c5194139c">&sect;</ulink>
1793 </para>
1794
1795 <para>
1796 In particular, report weight characters that are not printable ASCII
1797 in octal form (<literal>\<replaceable>nnn</replaceable></literal>),
1798 as <function>charout()</function> would render them. This avoids
1799 possibly producing an invalidly-encoded error message.
1800 </para>
1801 </listitem>
1802
1803 <listitem>
1804 <!--
1805 Author: Masahiko Sawada <[email protected]>
1806 Branch: master [7575215e0] 2026-07-16 11:50:10 -0700
1807 Branch: REL_19_STABLE [2a933deaa] 2026-07-16 11:50:16 -0700
1808 Branch: REL_18_STABLE [c31b0fca0] 2026-07-16 11:50:13 -0700
1809 -->
1810 <para>
1811 Reject out-of-range timestamp shift values
1812 in <function>uuidv7()</function> (Baji Shaik)
1813 <ulink url="&commit_baseurl;c31b0fca0">&sect;</ulink>
1814 </para>
1815
1816 <para>
1817 The shift value must not be so large as to produce a timestamp out
1818 of the range that a v7 UUID can represent. Previously, a garbage
1819 UUID value was produced.
1820 </para>
1821 </listitem>
1822
1823 <listitem>
1824 <!--
1825 Author: Michael Paquier <[email protected]>
1826 Branch: master Release: REL_19_BR [8bf257aeb] 2026-06-12 10:25:45 +0900
1827 Branch: REL_18_STABLE [4c777d6dd] 2026-06-12 10:25:49 +0900
1828 Branch: REL_17_STABLE [6c08cbb7a] 2026-06-12 10:25:51 +0900
1829 Branch: REL_16_STABLE [174076601] 2026-06-12 10:25:53 +0900
1830 Branch: REL_15_STABLE [1d8c72b2e] 2026-06-12 10:25:54 +0900
1831 Branch: REL_14_STABLE [41876c8d7] 2026-06-12 10:25:59 +0900
1832 Branch: master Release: REL_19_BR [0b74df66f] 2026-06-12 12:37:21 +0900
1833 Branch: REL_18_STABLE [0d145be2c] 2026-06-12 12:39:11 +0900
1834 Branch: REL_17_STABLE [940916549] 2026-06-12 12:39:17 +0900
1835 Branch: REL_16_STABLE [fac26fd41] 2026-06-12 12:39:22 +0900
1836 Branch: REL_15_STABLE [9618e790c] 2026-06-12 12:39:34 +0900
1837 Branch: REL_14_STABLE [a17f39aa2] 2026-06-12 12:39:40 +0900
1838 -->
1839 <para>
1840 Fix mishandling of namespace nodes in <function>xpath()</function>
1841 (Michael Paquier)
1842 <ulink url="&commit_baseurl;4c777d6dd">&sect;</ulink>
1843 <ulink url="&commit_baseurl;0d145be2c">&sect;</ulink>
1844 </para>
1845
1846 <para>
1847 This fix avoids an unexpected <quote>could not copy node</quote>
1848 error.
1849 </para>
1850 </listitem>
1851
1852 <listitem>
1853 <!--
1854 Author: Michael Paquier <[email protected]>
1855 Branch: master [7b12ae729] 2026-07-02 12:44:29 +0900
1856 Branch: REL_19_STABLE [5bbc9b300] 2026-07-02 12:44:31 +0900
1857 Branch: REL_18_STABLE [84001a04d] 2026-07-02 12:44:33 +0900
1858 Branch: REL_17_STABLE [ab35b8d25] 2026-07-02 12:44:36 +0900
1859 Branch: REL_18_STABLE [90789900b] 2026-07-02 15:06:05 +0900
1860 Branch: REL_17_STABLE [c768637d6] 2026-07-02 15:06:12 +0900
1861 -->
1862 <para>
1863 Fix <type>jsonpath</type>'s <function>.decimal</function> method to
1864 not throw a hard error for incorrect precision or scale (Ewan Young)
1865 <ulink url="&commit_baseurl;84001a04d">&sect;</ulink>
1866 <ulink url="&commit_baseurl;90789900b">&sect;</ulink>
1867 </para>
1868
1869 <para>
1870 Silent mode should suppress these errors, but failed to.
1871 </para>
1872 </listitem>
1873
1874 <listitem>
1875 <!--
1876 Author: Álvaro Herrera <[email protected]>
1877 Branch: master Release: REL_19_BR [7dd153259] 2026-06-11 16:17:58 +0200
1878 Branch: REL_18_STABLE [35d9a6263] 2026-06-11 16:17:58 +0200
1879 Branch: REL_17_STABLE [d0acd2535] 2026-06-11 16:17:58 +0200
1880 Branch: REL_16_STABLE [60abb3c73] 2026-06-11 16:17:58 +0200
1881 -->
1882 <para>
1883 Fix NULL-pointer crash when <literal>IS JSON</literal> or similar
1884 constructs have an argument that is of string category but lacks a
1885 cast to type <type>text</type> (Ayush Tiwari)
1886 <ulink url="&commit_baseurl;35d9a6263">&sect;</ulink>
1887 </para>
1888
1889 <para>
1890 There are no such data types in
1891 core <productname>PostgreSQL</productname>, but the problem is
1892 reachable with some extension types.
1893 </para>
1894 </listitem>
1895
1896 <listitem>
1897 <!--
1898 Author: Amit Langote <[email protected]>
1899 Branch: master [4c75cc786] 2026-07-07 08:27:32 +0900
1900 Branch: REL_19_STABLE [d30bfcbdd] 2026-07-07 08:27:19 +0900
1901 Branch: REL_18_STABLE [441e4c8d6] 2026-07-07 08:27:05 +0900
1902 Branch: REL_17_STABLE [71cd10cd2] 2026-07-07 08:26:50 +0900
1903 -->
1904 <para>
1905 Ensure that <literal>SQL/JSON</literal> <literal>ON EMPTY / ON ERROR
1906 DEFAULT</literal> values are coerced to the correct typmod (Ewan Young)
1907 <ulink url="&commit_baseurl;441e4c8d6">&sect;</ulink>
1908 </para>
1909
1910 <para>
1911 For example, the declared precision and scale of
1912 a <type>numeric</type> target column were not applied to the default
1913 value.
1914 </para>
1915 </listitem>
1916
1917 <listitem>
1918 <!--
1919 Author: David Rowley <[email protected]>
1920 Branch: master [b4dfae2ff] 2026-08-04 17:59:13 +1200
1921 Branch: REL_19_STABLE [7746f7492] 2026-08-04 17:59:58 +1200
1922 Branch: REL_18_STABLE [6298a41b4] 2026-08-04 18:00:27 +1200
1923 Branch: REL_17_STABLE [1416f304d] 2026-08-04 18:00:49 +1200
1924 Branch: REL_16_STABLE [86f42357c] 2026-08-04 18:01:10 +1200
1925 Branch: REL_15_STABLE [d782c97e1] 2026-08-04 18:01:31 +1200
1926 Branch: REL_14_STABLE [fec40878c] 2026-08-04 18:01:55 +1200
1927 -->
1928 <para>
1929 Avoid machine-dependent behavior when dividing the smallest
1930 possible <type>money</type> value by -1 (Andrey Rachitskiy)
1931 <ulink url="&commit_baseurl;6298a41b4">&sect;</ulink>
1932 </para>
1933 </listitem>
1934
1935 <listitem>
1936 <!--
1937 Author: Tom Lane <[email protected]>
1938 Branch: master [4e68b7e29] 2026-08-02 16:49:17 -0400
1939 Branch: REL_19_STABLE [df8407d7d] 2026-08-02 16:49:18 -0400
1940 Branch: REL_18_STABLE [81b1e7916] 2026-08-02 16:49:18 -0400
1941 Branch: REL_17_STABLE [634a8dcb8] 2026-08-02 16:49:18 -0400
1942 Branch: REL_16_STABLE [83336e3ed] 2026-08-02 16:49:18 -0400
1943 Branch: REL_15_STABLE [025228104] 2026-08-02 16:49:18 -0400
1944 Branch: REL_14_STABLE [dda622edc] 2026-08-02 16:49:18 -0400
1945 -->
1946 <para>
1947 Fix crash after out-of-memory failure partway through creation of a
1948 cache entry for a text search dictionary (Tom Lane)
1949 <ulink url="&commit_baseurl;81b1e7916">&sect;</ulink>
1950 </para>
1951 </listitem>
1952
1953 <listitem>
1954 <!--
1955 Author: Tom Lane <[email protected]>
1956 Branch: master [330a72052] 2026-08-02 13:22:39 -0400
1957 Branch: REL_19_STABLE [3fe4062cc] 2026-08-02 13:22:39 -0400
1958 Branch: REL_18_STABLE [4689ea9ce] 2026-08-02 13:22:39 -0400
1959 Branch: REL_17_STABLE [5fdea3aa3] 2026-08-02 13:22:39 -0400
1960 Branch: REL_16_STABLE [444038bb7] 2026-08-02 13:22:39 -0400
1961 Branch: REL_15_STABLE [0fb88979b] 2026-08-02 13:22:39 -0400
1962 Branch: REL_14_STABLE [cfc720ef4] 2026-08-02 13:22:39 -0400
1963 -->
1964 <para>
1965 Fix memory-safety bugs in processing of incorrect ispell/hunspell
1966 dictionary files (Andrey Rachitskiy)
1967 <ulink url="&commit_baseurl;4689ea9ce">&sect;</ulink>
1968 </para>
1969 </listitem>
1970
1971 <listitem>
1972 <!--
1973 Author: Alexander Korotkov <[email protected]>
1974 Branch: master Release: REL_19_BR [ce146621f] 2026-05-14 15:01:17 +0300
1975 Branch: REL_18_STABLE [1b0dd0815] 2026-05-14 15:06:27 +0300
1976 Branch: REL_17_STABLE [4dfae59a1] 2026-05-14 15:07:03 +0300
1977 Branch: master [c40819ebf] 2026-07-03 18:02:14 +0300
1978 Branch: REL_19_STABLE [8021cdceb] 2026-07-03 18:01:25 +0300
1979 Branch: REL_18_STABLE [3aaefe892] 2026-07-03 18:01:21 +0300
1980 Branch: REL_17_STABLE [4e49f68b7] 2026-07-03 18:01:03 +0300
1981 Branch: REL_16_STABLE [cc3fe7e2a] 2026-07-03 18:01:00 +0300
1982 -->
1983 <para>
1984 Prevent access to other sessions' temporary tables (Jim Jones,
1985 Daniil Davydov, Alexander Korotkov)
1986 <ulink url="&commit_baseurl;1b0dd0815">&sect;</ulink>
1987 <ulink url="&commit_baseurl;3aaefe892">&sect;</ulink>
1988 </para>
1989
1990 <para>
1991 Some code paths failed to prevent this, leading to silently wrong
1992 (inconsistent) results.
1993 </para>
1994 </listitem>
1995
1996 <listitem>
1997 <!--
1998 Author: Melanie Plageman <[email protected]>
1999 Branch: master Release: REL_19_BR [da6874635] 2026-04-21 11:03:05 -0400
2000 Branch: REL_18_STABLE [ed8050370] 2026-08-05 11:44:01 -0400
2001 -->
2002 <para>
2003 Prevent <quote>no empty local buffer available</quote> errors during
2004 temporary table access (Melanie Plageman)
2005 <ulink url="&commit_baseurl;ed8050370">&sect;</ulink>
2006 </para>
2007
2008 <para>
2009 Limit the number of local buffers that the read streaming mechanism
2010 is allowed to use. Previously, a large value
2011 of <varname>effective_io_concurrency</varname> could allow a single
2012 stream to use all the buffers, resulting in failure.
2013 </para>
2014 </listitem>
2015
2016 <listitem>
2017 <!--
2018 Author: Nathan Bossart <[email protected]>
2019 Branch: master [baab3268c] 2026-07-31 10:34:40 -0500
2020 Branch: REL_19_STABLE [b3331578b] 2026-07-31 10:34:40 -0500
2021 Branch: REL_18_STABLE [4cc49cb70] 2026-07-31 10:34:40 -0500
2022 Branch: REL_17_STABLE [288d4e83f] 2026-07-31 10:34:40 -0500
2023 -->
2024 <para>
2025 Fix the order in which autovacuum processes databases
2026 (Rustam Khamidullin)
2027 <ulink url="&commit_baseurl;4cc49cb70">&sect;</ulink>
2028 </para>
2029
2030 <para>
2031 It was unintentionally processing databases from lowest to highest
2032 score, when it should be doing the reverse.
2033 </para>
2034 </listitem>
2035
2036 <listitem>
2037 <!--
2038 Author: Melanie Plageman <[email protected]>
2039 Branch: master [112c26838] 2026-08-06 17:22:34 -0400
2040 Branch: REL_19_STABLE [fd90c3221] 2026-08-06 17:24:12 -0400
2041 Branch: REL_18_STABLE [585181e07] 2026-08-06 17:31:22 -0400
2042 Branch: master [69800557c] 2026-08-07 10:00:26 -0400
2043 Branch: REL_19_STABLE [55d01a10f] 2026-08-07 10:05:23 -0400
2044 Branch: REL_18_STABLE [7c25cdb1e] 2026-08-07 10:06:41 -0400
2045 -->
2046 <para>
2047 Restore full use of shared buffer pool
2048 in <command>VACUUM</command>'s wraparound failsafe mode
2049 (Melanie Plageman)
2050 <ulink url="&commit_baseurl;585181e07">&sect;</ulink>
2051 <ulink url="&commit_baseurl;7c25cdb1e">&sect;</ulink>
2052 </para>
2053
2054 <para>
2055 An ordinary <command>VACUUM</command> is limited to use just a few
2056 shared buffers, so as not to impinge too much on other processing.
2057 However, in failsafe mode we want to reclaim transaction IDs as
2058 quickly as possible, so that limit is supposed to be abandoned
2059 to allow vacuuming to proceed as fast as possible. This behavior
2060 was accidentally broken during refactoring in v18; restore it.
2061 </para>
2062 </listitem>
2063
2064 <listitem>
2065 <!--
2066 Author: Michael Paquier <[email protected]>
2067 Branch: master Release: REL_19_BR [b20c952ce] 2026-06-08 15:29:16 +0900
2068 Branch: REL_18_STABLE [4154a1482] 2026-06-08 15:29:19 +0900
2069 Branch: REL_17_STABLE [8ad414831] 2026-06-08 15:29:21 +0900
2070 -->
2071 <para>
2072 Fix memory leak in parallel vacuum worker processes (Baji Shaik)
2073 <ulink url="&commit_baseurl;4154a1482">&sect;</ulink>
2074 </para>
2075
2076 <para>
2077 Progress reports from a parallel worker leaked about 1kB per report,
2078 with the waste accumulating for the life of the worker process.
2079 </para>
2080 </listitem>
2081
2082 <listitem>
2083 <!--
2084 Author: Alexander Korotkov <[email protected]>
2085 Branch: master [8a045f760] 2026-07-28 10:50:22 +0200
2086 Branch: REL_19_STABLE [70dad584e] 2026-07-28 10:50:53 +0200
2087 Branch: REL_18_STABLE [7becb647d] 2026-07-28 10:52:59 +0200
2088 Branch: REL_17_STABLE [ba5e46329] 2026-07-28 10:56:27 +0200
2089 Branch: REL_16_STABLE [006ac761e] 2026-07-28 10:56:34 +0200
2090 Branch: REL_15_STABLE [7123abab7] 2026-07-28 10:56:38 +0200
2091 Branch: REL_14_STABLE [15fd7a3e2] 2026-07-28 10:56:39 +0200
2092 -->
2093 <para>
2094 Honor query cancel and vacuum delay during GIN index posting-tree
2095 cleanup (Paul Kim, Alexander Korotkov)
2096 <ulink url="&commit_baseurl;7becb647d">&sect;</ulink>
2097 </para>
2098
2099 <para>
2100 The posting tree for a common value can be large, so that this
2101 missed check could allow vacuum to run for a long time before
2102 noticing an interrupt.
2103 </para>
2104 </listitem>
2105
2106 <listitem>
2107 <!--
2108 Author: Peter Geoghegan <[email protected]>
2109 Branch: master [c9ea37231] 2026-07-17 15:53:10 -0400
2110 Branch: REL_19_STABLE [1d4c81ad6] 2026-07-17 15:53:07 -0400
2111 Branch: REL_18_STABLE [959b7fa2c] 2026-07-17 15:53:05 -0400
2112 Branch: REL_17_STABLE [355faed5a] 2026-07-17 15:53:02 -0400
2113 Branch: REL_16_STABLE [e58192546] 2026-07-17 15:53:00 -0400
2114 Branch: REL_15_STABLE [126141425] 2026-07-17 15:52:58 -0400
2115 Branch: REL_14_STABLE [e4ad22eb0] 2026-07-17 15:52:56 -0400
2116 -->
2117 <para>
2118 Fix possible mis-decoding of index tuples during GiST and SP-GiST
2119 index-only scans (Peter Geoghegan)
2120 <ulink url="&commit_baseurl;959b7fa2c">&sect;</ulink>
2121 </para>
2122
2123 <para>
2124 This error could lead to emitting corrupted data from an index-only
2125 scan plan. The only affected core opclass is GiST's range_ops, and
2126 it could only fail if the range column were not the first index
2127 column.
2128 </para>
2129 </listitem>
2130
2131 <listitem>
2132 <!--
2133 Author: Melanie Plageman <[email protected]>
2134 Branch: master [a2fd8d65a] 2026-07-15 15:51:05 -0400
2135 Branch: REL_19_STABLE [7a103928a] 2026-07-15 15:52:43 -0400
2136 Branch: REL_18_STABLE [eabc9a9dd] 2026-07-15 15:54:54 -0400
2137 Branch: REL_17_STABLE [768ae083e] 2026-07-15 15:56:06 -0400
2138 Branch: REL_16_STABLE [0fd5595aa] 2026-07-15 15:58:15 -0400
2139 -->
2140 <para>
2141 Ensure that the new last block of a bulk-extended table is added to
2142 its free space map promptly (Jingtang Zhang)
2143 <ulink url="&commit_baseurl;eabc9a9dd">&sect;</ulink>
2144 </para>
2145
2146 <para>
2147 An off-by-one error caused the last block of a multi-block table
2148 extension to not be marked as free in the map. This would
2149 eventually get corrected by vacuum, but meanwhile the space wouldn't
2150 be used.
2151 </para>
2152 </listitem>
2153
2154 <listitem>
2155 <!--
2156 Author: Tom Lane <[email protected]>
2157 Branch: master Release: REL_19_BR [ef01ca6db] 2026-06-22 18:03:23 -0400
2158 Branch: REL_18_STABLE [ac6a58a70] 2026-06-22 18:03:23 -0400
2159 Branch: REL_17_STABLE [011eedcdc] 2026-06-22 18:03:23 -0400
2160 -->
2161 <para>
2162 Avoid possible double-free or infinite error recovery loop in
2163 resource cleanup during transaction abort (Tom Lane)
2164 <ulink url="&commit_baseurl;ac6a58a70">&sect;</ulink>
2165 </para>
2166 </listitem>
2167
2168 <listitem>
2169 <!--
2170 Author: Tom Lane <[email protected]>
2171 Branch: master Release: REL_19_BR [f25a07b2d] 2026-06-19 12:52:00 -0400
2172 Branch: REL_18_STABLE [aa80c34c8] 2026-06-19 12:52:00 -0400
2173 Branch: REL_17_STABLE [f0a831ef3] 2026-06-19 12:52:00 -0400
2174 Branch: REL_16_STABLE [9951e3d38] 2026-06-19 12:52:00 -0400
2175 Branch: REL_15_STABLE [4647ac142] 2026-06-19 12:52:00 -0400
2176 Branch: REL_14_STABLE [4b3bc6b71] 2026-06-19 12:52:00 -0400
2177 -->
2178 <para>
2179 When creating directories, tolerate concurrent creation of the same
2180 directory (Andrew Dunstan, Tom Lane)
2181 <ulink url="&commit_baseurl;aa80c34c8">&sect;</ulink>
2182 </para>
2183 </listitem>
2184
2185 <listitem>
2186 <!--
2187 Author: David Rowley <[email protected]>
2188 Branch: master Release: REL_19_BR [dc5116780] 2026-06-19 15:26:18 +1200
2189 Branch: REL_18_STABLE [e9692de1d] 2026-06-19 15:26:51 +1200
2190 -->
2191 <para>
2192 Fix JIT-compiled tuple deconstruction code to account correctly for
2193 virtual generated columns (David Rowley)
2194 <ulink url="&commit_baseurl;e9692de1d">&sect;</ulink>
2195 </para>
2196 </listitem>
2197
2198 <listitem>
2199 <!--
2200 Author: Heikki Linnakangas <[email protected]>
2201 Branch: master Release: REL_19_BR [2fbb21170] 2026-05-27 18:41:14 +0300
2202 Branch: REL_18_STABLE [c8cd3d697] 2026-05-27 18:36:28 +0300
2203 Branch: REL_17_STABLE [3a9909eda] 2026-05-27 18:36:51 +0300
2204 Branch: REL_16_STABLE [d9bc0d96c] 2026-05-27 18:37:12 +0300
2205 Branch: REL_15_STABLE [5fa137727] 2026-05-27 18:37:32 +0300
2206 Branch: REL_14_STABLE [5100bdbd3] 2026-05-27 18:37:56 +0300
2207 Branch: master Release: REL_19_BR [fd93ee100] 2026-05-27 18:41:03 +0300
2208 Branch: REL_18_STABLE [f9d5a52da] 2026-05-27 18:36:25 +0300
2209 Branch: REL_17_STABLE [c1588f92a] 2026-05-27 18:36:46 +0300
2210 Branch: REL_16_STABLE [d44cd4674] 2026-05-27 18:37:04 +0300
2211 Branch: REL_15_STABLE [ef3d7b15e] 2026-05-27 18:37:27 +0300
2212 Branch: REL_14_STABLE [36b6ed260] 2026-05-27 18:37:48 +0300
2213 -->
2214 <para>
2215 Prevent creation of dangling object dependencies by acquiring a
2216 shared lock on any object being depended on (Bertrand Drouvot)
2217 <ulink url="&commit_baseurl;c8cd3d697">&sect;</ulink>
2218 <ulink url="&commit_baseurl;f9d5a52da">&sect;</ulink>
2219 </para>
2220
2221 <para>
2222 The shared lock will conflict with any attempt to drop the
2223 depended-on object, eliminating the race condition that formerly
2224 existed. For example, if one session drops a schema (that appears
2225 empty to it) concurrently with some other session creating a
2226 function in that schema, previously both transactions could commit,
2227 leaving an invalid function definition behind. Now, one transaction
2228 or the other will fail.
2229 </para>
2230 </listitem>
2231
2232 <listitem>
2233 <!--
2234 Author: Peter Geoghegan <[email protected]>
2235 Branch: master [ce3f19e26] 2026-07-25 12:01:35 -0400
2236 Branch: REL_19_STABLE [2aa3c6d1f] 2026-07-25 12:01:34 -0400
2237 Branch: REL_18_STABLE [d560e730e] 2026-07-25 12:01:32 -0400
2238 Branch: REL_17_STABLE [8434c9385] 2026-07-25 12:01:30 -0400
2239 Branch: REL_16_STABLE [e321faaae] 2026-07-25 12:01:28 -0400
2240 Branch: REL_15_STABLE [5d18105ca] 2026-07-25 12:01:26 -0400
2241 Branch: REL_14_STABLE [2fc3e1b44] 2026-07-25 12:01:24 -0400
2242 -->
2243 <para>
2244 Fix race condition in conflict detection
2245 for <literal>SERIALIZABLE</literal> isolation mode
2246 (Peter Geoghegan)
2247 <ulink url="&commit_baseurl;d560e730e">&sect;</ulink>
2248 </para>
2249
2250 <para>
2251 A conflict could be missed when examining an initially-empty btree
2252 index, allowing failure of serializability due to improperly
2253 allowing conflicting transactions to commit.
2254 </para>
2255 </listitem>
2256
2257 <listitem>
2258 <!--
2259 Author: Masahiko Sawada <[email protected]>
2260 Branch: master Release: REL_19_BR [d79bf7612] 2026-05-27 16:25:56 -0700
2261 Branch: REL_18_STABLE [1a9b1cc18] 2026-05-27 16:25:59 -0700
2262 Branch: REL_17_STABLE [a651b8a89] 2026-05-27 16:26:02 -0700
2263 Branch: REL_16_STABLE [cdb9b2830] 2026-05-27 16:26:05 -0700
2264 Branch: REL_15_STABLE [159324a73] 2026-05-27 16:26:08 -0700
2265 -->
2266 <para>
2267 Fix race condition in ProcSignalBarrier code (Masahiko Sawada)
2268 <ulink url="&commit_baseurl;1a9b1cc18">&sect;</ulink>
2269 </para>
2270
2271 <para>
2272 This error could result in processes getting stuck, typically after
2273 reporting <quote>still waiting for backend with
2274 PID <replaceable>nnnn</replaceable> to accept
2275 ProcSignalBarrier</quote>.
2276 </para>
2277 </listitem>
2278
2279 <listitem>
2280 <!--
2281 Author: Michael Paquier <[email protected]>
2282 Branch: master Release: REL_19_BR [563104523] 2026-05-27 14:48:56 +0900
2283 Branch: REL_18_STABLE [ae08eb168] 2026-05-27 14:48:59 +0900
2284 Branch: REL_17_STABLE [d489c4439] 2026-05-27 14:49:01 +0900
2285 Branch: REL_16_STABLE [65d04df60] 2026-05-27 14:49:02 +0900
2286 Branch: REL_15_STABLE [d5cc6df60] 2026-05-27 14:49:04 +0900
2287 Branch: REL_14_STABLE [8007d1185] 2026-05-27 14:52:31 +0900
2288 Branch: master Release: REL_19_BR [84b9d6bce] 2026-05-27 17:19:20 +0900
2289 Branch: REL_18_STABLE [12c9b8b42] 2026-05-27 17:19:53 +0900
2290 Branch: REL_17_STABLE [e14b4ea4a] 2026-05-27 17:19:55 +0900
2291 Branch: REL_16_STABLE [4e8edf53f] 2026-05-27 17:19:56 +0900
2292 Branch: REL_15_STABLE [e786fb5aa] 2026-05-27 17:19:58 +0900
2293 Branch: REL_14_STABLE [db4d12fc9] 2026-05-27 17:20:00 +0900
2294 -->
2295 <para>
2296 Fix race conditions when a set of processes that belong to the same
2297 lock group exit at the same time (Vlad Lesin)
2298 <ulink url="&commit_baseurl;ae08eb168">&sect;</ulink>
2299 <ulink url="&commit_baseurl;12c9b8b42">&sect;</ulink>
2300 </para>
2301
2302 <para>
2303 These errors could lead to PANIC aborts, with messages such
2304 as <quote>latch already owned</quote>. The issue does not normally
2305 arise in regular parallel query, since the leader won't exit before
2306 seeing its workers finish; but some extensions reach the problem.
2307 </para>
2308 </listitem>
2309
2310 <listitem>
2311 <!--
2312 Author: Melanie Plageman <[email protected]>
2313 Branch: master [10911fde0] 2026-07-15 17:24:49 -0400
2314 Branch: REL_19_STABLE [56bf5fa5d] 2026-07-15 17:32:17 -0400
2315 Branch: REL_18_STABLE [d0fb1da21] 2026-07-15 17:37:34 -0400
2316 Branch: REL_17_STABLE [7edec8b57] 2026-07-15 17:43:38 -0400
2317 Branch: master [ed62d26ca] 2026-07-15 17:24:49 -0400
2318 Branch: REL_19_STABLE [b01c31eef] 2026-07-15 17:32:17 -0400
2319 Branch: REL_18_STABLE [f581fa729] 2026-07-15 17:37:34 -0400
2320 Branch: REL_17_STABLE [c0d9864f5] 2026-07-15 17:43:38 -0400
2321 Branch: master [5174d157a] 2026-07-15 17:24:49 -0400
2322 Branch: REL_19_STABLE [9171f77db] 2026-07-15 17:32:17 -0400
2323 Branch: REL_18_STABLE [4d7feebfb] 2026-07-15 17:37:34 -0400
2324 Branch: REL_17_STABLE [067213430] 2026-07-15 17:43:38 -0400
2325 -->
2326 <para>
2327 Fix WAL logging of operations that clear bits in tables' visibility
2328 maps (Melanie Plageman, Andres Freund)
2329 <ulink url="&commit_baseurl;d0fb1da21">&sect;</ulink>
2330 <ulink url="&commit_baseurl;f581fa729">&sect;</ulink>
2331 <ulink url="&commit_baseurl;4d7feebfb">&sect;</ulink>
2332 </para>
2333
2334 <para>
2335 Such VM changes were missed by the WAL summarizer, potentially
2336 leading to incorrect incremental backups. We also failed to log
2337 full-page images of such VM pages when needed, potentially allowing
2338 torn page writes to go uncorrected. This could lead to misbehavior
2339 later, such as wrong results from index-only scans.
2340 </para>
2341 </listitem>
2342
2343 <listitem>
2344 <!--
2345 Author: Robert Haas <[email protected]>
2346 Branch: master [3e8a0c1b0] 2026-07-31 11:55:54 -0400
2347 Branch: REL_19_STABLE [dfb96277d] 2026-07-31 11:56:52 -0400
2348 Branch: REL_18_STABLE [18f0de6b8] 2026-07-31 11:57:07 -0400
2349 Branch: REL_17_STABLE [499d9eabb] 2026-07-31 11:57:44 -0400
2350 Branch: master [8767a10cb] 2026-07-22 08:47:44 -0400
2351 Branch: REL_19_STABLE [bdcea66f0] 2026-07-22 08:49:39 -0400
2352 Branch: REL_18_STABLE [1d299d6ab] 2026-07-22 08:49:30 -0400
2353 Branch: REL_17_STABLE [d28cdf46e] 2026-07-22 08:49:00 -0400
2354 -->
2355 <para>
2356 Prevent WAL summarizer process from getting stuck at a timeline
2357 switch (Robert Haas)
2358 <ulink url="&commit_baseurl;18f0de6b8">&sect;</ulink>
2359 <ulink url="&commit_baseurl;1d299d6ab">&sect;</ulink>
2360 </para>
2361 </listitem>
2362
2363 <listitem>
2364 <!--
2365 Author: Michael Paquier <[email protected]>
2366 Branch: master Release: REL_19_BR [eb4e7224a] 2026-06-11 17:28:57 +0900
2367 Branch: REL_18_STABLE [b4bd13850] 2026-06-11 17:29:38 +0900
2368 Branch: REL_17_STABLE [16b89ff04] 2026-06-11 17:29:39 +0900
2369 Branch: REL_16_STABLE [8cd687c44] 2026-06-11 17:29:41 +0900
2370 Branch: REL_16_STABLE [2a04624da] 2026-06-11 14:43:07 +0900
2371 Branch: master Release: REL_19_BR [a8ee70bd5] 2026-06-12 11:44:11 +0900
2372 Branch: REL_18_STABLE [4bff3aa51] 2026-06-12 11:44:14 +0900
2373 Branch: REL_17_STABLE [ab5334d8b] 2026-06-12 11:44:16 +0900
2374 Branch: REL_16_STABLE [d9b49e5b4] 2026-06-12 11:44:19 +0900
2375 -->
2376 <para>
2377 Fix race with timeline selection in logical decoding during standby
2378 promotion (Bertrand Drouvot)
2379 <ulink url="&commit_baseurl;b4bd13850">&sect;</ulink>
2380 <ulink url="&commit_baseurl;4bff3aa51">&sect;</ulink>
2381 </para>
2382
2383 <para>
2384 Logical decoding being performed on the standby could fail with
2385 a <quote>requested WAL segment has already been removed</quote>
2386 error. A repeat attempt would succeed, so there was no permanent
2387 problem but there was an availability hazard.
2388 </para>
2389 </listitem>
2390
2391 <listitem>
2392 <!--
2393 Author: Michael Paquier <[email protected]>
2394 Branch: master Release: REL_19_BR [c37b38806] 2026-05-23 08:10:07 +0900
2395 Branch: REL_18_STABLE [b903d1792] 2026-05-23 08:10:12 +0900
2396 Branch: REL_17_STABLE [c89499a79] 2026-05-23 08:10:14 +0900
2397 Branch: REL_16_STABLE [e037a4199] 2026-05-23 08:10:15 +0900
2398 Branch: REL_15_STABLE [065cbfb88] 2026-05-23 08:10:17 +0900
2399 Branch: REL_14_STABLE [e18b77153] 2026-05-23 08:10:18 +0900
2400 -->
2401 <para>
2402 Avoid exposing a WAL receiver's full connection string during timeline
2403 jumps (Chao Li)
2404 <ulink url="&commit_baseurl;b903d1792">&sect;</ulink>
2405 </para>
2406
2407 <para>
2408 The <structname>pg_stat_wal_receiver</structname> view should show a
2409 sanitized version of the connection string, without sensitive data.
2410 But it transiently showed the full string when we re-use an existing
2411 WAL receiver.
2412 </para>
2413 </listitem>
2414
2415 <listitem>
2416 <!--
2417 Author: Noah Misch <[email protected]>
2418 Branch: master Release: REL_19_BR [bf7d19be9] 2026-05-16 18:01:35 -0700
2419 Branch: REL_18_STABLE [dc3db3a83] 2026-05-16 18:01:38 -0700
2420 Branch: REL_17_STABLE [15f4e3d0c] 2026-05-16 18:01:39 -0700
2421 Branch: REL_16_STABLE [59759e1a5] 2026-05-16 18:01:39 -0700
2422 Branch: REL_15_STABLE [871d4f5b6] 2026-05-16 18:01:40 -0700
2423 Branch: REL_14_STABLE [510a05f07] 2026-05-16 18:01:46 -0700
2424 -->
2425 <para>
2426 Use run-time checks, not just Asserts, to verify the correct number
2427 of columns in tuples received during logical replication (Varik
2428 Matevosyan)
2429 <ulink url="&commit_baseurl;dc3db3a83">&sect;</ulink>
2430 </para>
2431
2432 <para>
2433 A malicious or buggy publisher could send inconsistent numbers of
2434 columns. While we could not find a scenario in which this would
2435 have serious ill effects, extra caution seems warranted.
2436 </para>
2437 </listitem>
2438
2439 <listitem>
2440 <!--
2441 Author: Tom Lane <[email protected]>
2442 Branch: master Release: REL_19_BR [a75bd485b] 2026-06-15 15:35:37 -0400
2443 Branch: REL_18_STABLE [abb582555] 2026-06-15 15:35:37 -0400
2444 Branch: REL_17_STABLE [14810cc0d] 2026-06-15 15:35:37 -0400
2445 Branch: REL_16_STABLE [26d6c19d0] 2026-06-15 15:35:37 -0400
2446 Branch: REL_15_STABLE [819e5b964] 2026-06-15 15:35:37 -0400
2447 Branch: REL_14_STABLE [2a00840e8] 2026-06-15 15:35:37 -0400
2448 -->
2449 <para>
2450 Clean up quoting of string parameters within constructed replication
2451 commands (Tom Lane)
2452 <ulink url="&commit_baseurl;abb582555">&sect;</ulink>
2453 </para>
2454
2455 <para>
2456 Various places that generate replication commands were not being
2457 adequately careful about quoting replication slot names and other
2458 parameters that need to be inserted into those commands. This could
2459 result in unexpected syntax errors in those commands. In principle,
2460 a crafted replication slot name could result in SQL injection; but
2461 such a scenario seems very unlikely to occur in practice, since
2462 replication operations can only be invoked by highly-privileged
2463 users and there is no reason for them to use a slot name coming from
2464 an untrustworthy source.
2465 </para>
2466 </listitem>
2467
2468 <listitem>
2469 <!--
2470 Author: Masahiko Sawada <[email protected]>
2471 Branch: master [acaa100f9] 2026-07-28 12:33:28 -0700
2472 Branch: REL_19_STABLE [2289e65e1] 2026-07-28 12:33:31 -0700
2473 Branch: REL_18_STABLE [b563fc6bd] 2026-07-28 12:33:35 -0700
2474 Branch: REL_17_STABLE [8c4519c71] 2026-07-28 12:33:40 -0700
2475 Branch: REL_16_STABLE [744618346] 2026-07-28 12:33:43 -0700
2476 Branch: REL_15_STABLE [0dbfb8520] 2026-07-28 12:33:47 -0700
2477 Branch: REL_14_STABLE [c2d34db0a] 2026-07-28 12:33:50 -0700
2478 -->
2479 <para>
2480 Fix logical decoding of empty prepared transactions (Masahiko Sawada)
2481 <ulink url="&commit_baseurl;b563fc6bd">&sect;</ulink>
2482 </para>
2483
2484 <para>
2485 A prepared transaction that did not cause any decodable updates could
2486 result in sending <command>COMMIT/ROLLBACK PREPARED</command> to the
2487 output plugin with no preceding <command>PREPARE</command>. For the
2488 built-in subscriber this breaks replication, and other plugins will
2489 probably not like it either.
2490 </para>
2491 </listitem>
2492
2493 <listitem>
2494 <!--
2495 Author: Fujii Masao <[email protected]>
2496 Branch: master [8e684ce11] 2026-06-30 08:48:47 +0900
2497 Branch: REL_19_STABLE [22af34b98] 2026-06-30 08:50:08 +0900
2498 Branch: REL_18_STABLE [627605713] 2026-06-30 08:50:50 +0900
2499 Branch: REL_17_STABLE [a1ed6a9a0] 2026-06-30 08:51:22 +0900
2500 Branch: REL_16_STABLE [913d3b610] 2026-06-30 08:51:51 +0900
2501 Branch: REL_15_STABLE [d2980067b] 2026-06-30 08:52:50 +0900
2502 -->
2503 <para>
2504 Fix corruption of unlogged sequences after standby promotion
2505 (Fujii Masao)
2506 <ulink url="&commit_baseurl;627605713">&sect;</ulink>
2507 </para>
2508
2509 <para>
2510 Previously, if an unlogged sequence was created on the primary and
2511 replicated to a standby, accessing the sequence after promoting the
2512 standby could fail with <quote>bad magic number in sequence</quote>
2513 or related errors.
2514 </para>
2515 </listitem>
2516
2517 <listitem>
2518 <!--
2519 Author: Álvaro Herrera <[email protected]>
2520 Branch: master [b614de487] 2026-07-29 17:15:45 +0200
2521 Branch: REL_19_STABLE [bef46aed3] 2026-07-29 17:15:45 +0200
2522 Branch: REL_18_STABLE [331016322] 2026-07-29 17:15:45 +0200
2523 Branch: REL_17_STABLE [2cf28d1b9] 2026-07-29 17:15:45 +0200
2524 Branch: REL_16_STABLE [5dbeb69bc] 2026-07-29 17:15:45 +0200
2525 Branch: REL_15_STABLE [8f64cc83f] 2026-07-29 17:15:45 +0200
2526 Branch: REL_14_STABLE [5fb3c6389] 2026-07-29 17:15:45 +0200
2527 -->
2528 <para>
2529 Fix cascading standby reconnect failure after archive fallback
2530 (Marco Nenciarini)
2531 <ulink url="&commit_baseurl;331016322">&sect;</ulink>
2532 </para>
2533
2534 <para>
2535 A cascading standby could fail to reconnect to its upstream standby
2536 with <quote>requested starting point ... is ahead of the WAL flush
2537 position</quote> after falling back to archive recovery.
2538 </para>
2539 </listitem>
2540
2541 <listitem>
2542 <!--
2543 Author: Fujii Masao <[email protected]>
2544 Branch: master [b59783502] 2026-08-08 00:09:05 +0900
2545 Branch: REL_19_STABLE [7673dfe77] 2026-08-08 00:10:00 +0900
2546 Branch: REL_18_STABLE [311e66df9] 2026-08-08 00:10:06 +0900
2547 -->
2548 <para>
2549 Prevent accepting hot-standby connections before WAL replay has
2550 reached a consistent database state (Nikhil Sontakke)
2551 <ulink url="&commit_baseurl;311e66df9">&sect;</ulink>
2552 </para>
2553 </listitem>
2554
2555 <listitem>
2556 <!--
2557 Author: Alexander Korotkov <[email protected]>
2558 Branch: master Release: REL_19_BR [bec61f593] 2026-05-27 02:27:32 +0300
2559 Branch: REL_18_STABLE [97b5c5aaa] 2026-05-27 02:28:39 +0300
2560 Branch: REL_17_STABLE [4a375527a] 2026-05-27 02:28:49 +0300
2561 -->
2562 <para>
2563 Do not try to clear
2564 <structname>pg_database</structname>.<structfield>dathasloginevt</structfield>
2565 locally on a standby server (Ayush Tiwari)
2566 <ulink url="&commit_baseurl;97b5c5aaa">&sect;</ulink>
2567 </para>
2568
2569 <para>
2570 Event trigger cleanup tried to perform that action on standby
2571 servers as well as the primary. That can't work on a standby,
2572 and there's no need anyway since replay of the primary's database
2573 change will soon fix it.
2574 </para>
2575 </listitem>
2576
2577 <listitem>
2578 <!--
2579 Author: Amit Kapila <[email protected]>
2580 Branch: master Release: REL_19_BR [bdae2c20e] 2026-06-18 09:50:33 +0530
2581 Branch: REL_18_STABLE [08458bcae] 2026-06-18 09:42:56 +0530
2582 Branch: REL_17_STABLE [ea834d747] 2026-06-18 09:35:53 +0530
2583 -->
2584 <para>
2585 Avoid race condition while dropping obsolete replication slots
2586 (Xuneng Zhou)
2587 <ulink url="&commit_baseurl;08458bcae">&sect;</ulink>
2588 </para>
2589
2590 <para>
2591 An incorrect unlock and log message could occur if another session
2592 immediately re-used the dropped slot's shared-memory entry.
2593 </para>
2594 </listitem>
2595
2596 <listitem>
2597 <!--
2598 Author: Fujii Masao <[email protected]>
2599 Branch: master Release: REL_19_BR [f2081a780] 2026-06-03 18:44:56 +0900
2600 Branch: REL_18_STABLE [f833c9207] 2026-06-03 18:46:49 +0900
2601 Branch: REL_17_STABLE [080d61f07] 2026-06-03 18:47:10 +0900
2602 Branch: REL_16_STABLE [51e79222c] 2026-06-03 18:47:31 +0900
2603 Branch: REL_15_STABLE [a4eb59d40] 2026-06-03 18:47:46 +0900
2604 Branch: REL_14_STABLE [968c50845] 2026-06-03 18:47:52 +0900
2605 -->
2606 <para>
2607 Avoid race condition while dropping ephemeral replication slots
2608 (Zhijie Hou)
2609 <ulink url="&commit_baseurl;f833c9207">&sect;</ulink>
2610 </para>
2611
2612 <para>
2613 The slot-releasing code performed some additional updates to the
2614 replication slot's shared-memory entry after releasing the slot.
2615 This is unsafe since another session could immediately re-use the
2616 dropped slot's shared-memory entry. Skip those updates in the case
2617 of an ephemeral slot.
2618 </para>
2619 </listitem>
2620
2621 <listitem>
2622 <!--
2623 Author: Fujii Masao <[email protected]>
2624 Branch: master Release: REL_19_BR [422e54e30] 2026-05-13 11:44:31 +0900
2625 Branch: REL_18_STABLE [d9cd9b4d7] 2026-05-13 11:46:08 +0900
2626 Branch: REL_17_STABLE [f2acab534] 2026-05-13 11:46:12 +0900
2627 Branch: REL_16_STABLE [d140237da] 2026-05-13 11:46:17 +0900
2628 Branch: REL_15_STABLE [b5f7e7569] 2026-05-13 11:46:21 +0900
2629 Branch: REL_14_STABLE [e3c4e3746] 2026-05-13 11:46:26 +0900
2630 -->
2631 <para>
2632 Fix stale progress reports during logical replication table
2633 synchronization (Shinya Kato)
2634 <ulink url="&commit_baseurl;d9cd9b4d7">&sect;</ulink>
2635 </para>
2636
2637 <para>
2638 Previously, the <structname>pg_stat_progress_copy</structname> view
2639 in the subscriber would continue to show the
2640 initial <command>COPY</command> operation as active even after the
2641 data copy had finished. The stale entry remained visible until
2642 synchronization caught up with the publisher.
2643 </para>
2644 </listitem>
2645
2646 <listitem>
2647 <!--
2648 Author: Fujii Masao <[email protected]>
2649 Branch: master [55f0a13e9] 2026-07-01 23:04:18 +0900
2650 Branch: REL_19_STABLE [b70000837] 2026-07-01 23:05:04 +0900
2651 Branch: REL_18_STABLE [e7564ee8c] 2026-07-01 23:05:12 +0900
2652 Branch: REL_17_STABLE [e2ea6bfed] 2026-07-01 23:05:34 +0900
2653 Branch: REL_16_STABLE [7cbd80340] 2026-07-01 23:06:43 +0900
2654 Branch: REL_15_STABLE [cf7530cf7] 2026-07-01 23:06:49 +0900
2655 Branch: REL_18_STABLE [e2ad214dd] 2026-07-06 09:46:15 +0900
2656 Branch: REL_17_STABLE [a240e8cd2] 2026-07-06 09:47:56 +0900
2657 Branch: REL_16_STABLE [fffa4d870] 2026-07-06 09:48:01 +0900
2658 Branch: REL_15_STABLE [a8fb98b7b] 2026-07-06 09:48:06 +0900
2659 -->
2660 <para>
2661 Clear base backup progress on backup failure (Chao Li)
2662 <ulink url="&commit_baseurl;e7564ee8c">&sect;</ulink>
2663 <ulink url="&commit_baseurl;e2ad214dd">&sect;</ulink>
2664 </para>
2665
2666 <para>
2667 Previously the <structname>pg_stat_progress_basebackup</structname>
2668 view would continue to show a stale progress entry after a failure,
2669 until the replication client
2670 disconnected. <application>pg_basebackup</application> normally
2671 disconnects immediately, but other clients might not.
2672 </para>
2673 </listitem>
2674
2675 <listitem>
2676 <!--
2677 Author: Michael Paquier <[email protected]>
2678 Branch: master Release: REL_19_BR [850b9218c] 2026-06-18 11:49:30 +0900
2679 Branch: REL_18_STABLE [5cc59834b] 2026-06-18 11:49:34 +0900
2680 Branch: REL_17_STABLE [2e0c61aed] 2026-06-18 11:49:36 +0900
2681 Branch: REL_16_STABLE [bf4616b59] 2026-06-18 11:49:39 +0900
2682 Branch: REL_15_STABLE [1e9e62193] 2026-06-18 11:49:41 +0900
2683 Branch: REL_18_STABLE [8a4f389dd] 2026-06-18 14:48:37 +0900
2684 Branch: REL_17_STABLE [39e649d44] 2026-06-18 14:48:40 +0900
2685 Branch: REL_16_STABLE [7c457ea15] 2026-06-18 14:48:42 +0900
2686 Branch: REL_15_STABLE [75aca8b93] 2026-06-18 14:48:43 +0900
2687 Branch: REL_18_STABLE [fe464e9e6] 2026-06-23 07:58:04 +0900
2688 Branch: REL_17_STABLE [afb076b29] 2026-06-23 07:59:00 +0900
2689 Branch: REL_16_STABLE [e34b1ff5d] 2026-06-23 07:59:02 +0900
2690 Branch: REL_15_STABLE [9e4771825] 2026-06-23 07:59:03 +0900
2691 -->
2692 <para>
2693 Fix possible PANIC due to concurrent drop of pgstats entries
2694 when <varname>track_functions</varname> is enabled (Sami Imseih,
2695 Michael Paquier)
2696 <ulink url="&commit_baseurl;5cc59834b">&sect;</ulink>
2697 <ulink url="&commit_baseurl;8a4f389dd">&sect;</ulink>
2698 <ulink url="&commit_baseurl;fe464e9e6">&sect;</ulink>
2699 </para>
2700 </listitem>
2701
2702 <listitem>
2703 <!--
2704 Author: Michael Paquier <[email protected]>
2705 Branch: master [4069df21b] 2026-08-07 14:23:28 +0900
2706 Branch: REL_19_STABLE [89fc6a7c1] 2026-08-07 14:23:33 +0900
2707 Branch: REL_18_STABLE [2fd8d45ec] 2026-08-07 14:23:35 +0900
2708 Branch: REL_17_STABLE [fc9283b21] 2026-08-07 14:23:36 +0900
2709 Branch: REL_16_STABLE [636bcd6a5] 2026-08-07 14:23:38 +0900
2710 Branch: REL_15_STABLE [10e20e59e] 2026-08-07 14:23:39 +0900
2711 -->
2712 <para>
2713 Clean up broken local pgstats entry after failing to obtain space for
2714 the corresponding shared hashtable entry (Niall Newman)
2715 <ulink url="&commit_baseurl;2fd8d45ec">&sect;</ulink>
2716 </para>
2717
2718 <para>
2719 Failure to do this led to a null-pointer dereference the next time
2720 the local entry was used.
2721 </para>
2722 </listitem>
2723
2724 <listitem>
2725 <!--
2726 Author: Michael Paquier <[email protected]>
2727 Branch: master Release: REL_19_BR [3048e8130] 2026-06-17 16:05:11 +0900
2728 Branch: REL_18_STABLE [13f940b4b] 2026-06-17 16:05:37 +0900
2729 -->
2730 <para>
2731 Avoid recording incorrect I/O operation statistics after a failed
2732 read or write (Bertrand Drouvot)
2733 <ulink url="&commit_baseurl;13f940b4b">&sect;</ulink>
2734 </para>
2735 </listitem>
2736
2737 <listitem>
2738 <!--
2739 Author: Richard Guo <[email protected]>
2740 Branch: master Release: REL_19_BR [4015abe14] 2026-06-24 09:09:48 +0900
2741 Branch: REL_18_STABLE [e430ecc59] 2026-06-24 09:11:56 +0900
2742 Branch: REL_17_STABLE [d424d06ed] 2026-06-24 09:14:06 +0900
2743 Branch: REL_16_STABLE [3854f4afc] 2026-06-24 09:15:08 +0900
2744 Branch: REL_15_STABLE [9b2a6ccc4] 2026-06-24 09:16:24 +0900
2745 Branch: REL_14_STABLE [e520ad34b] 2026-06-24 09:17:36 +0900
2746 -->
2747 <para>
2748 In <application>PL/Perl</application>, avoid NULL pointer
2749 dereference crash when working with an
2750 invalid <type>PostgreSQL::InServer::ARRAY</type> object (Xing Guo)
2751 <ulink url="&commit_baseurl;e430ecc59">&sect;</ulink>
2752 </para>
2753 </listitem>
2754
2755 <listitem>
2756 <!--
2757 Author: Richard Guo <[email protected]>
2758 Branch: master Release: REL_19_BR [8612f0b7c] 2026-06-29 11:38:39 +0900
2759 Branch: REL_18_STABLE [53482fcb9] 2026-06-29 11:39:50 +0900
2760 Branch: REL_17_STABLE [3dc59c173] 2026-06-29 11:40:49 +0900
2761 Branch: REL_16_STABLE [e92f23bde] 2026-06-29 11:41:50 +0900
2762 Branch: REL_15_STABLE [12bff46ff] 2026-06-29 11:43:26 +0900
2763 Branch: REL_14_STABLE [0b7719f74] 2026-06-29 11:44:35 +0900
2764 Branch: REL_14_STABLE [309dc4526] 2026-06-29 14:21:15 +0900
2765 -->
2766 <para>
2767 In <application>PL/Python</application>, properly check for errors
2768 when working with sequence and mapping objects (Richard Guo)
2769 <ulink url="&commit_baseurl;53482fcb9">&sect;</ulink>
2770 </para>
2771
2772 <para>
2773 Previously, a broken object or an unhandled exception could result
2774 in a NULL pointer dereference crash.
2775 </para>
2776 </listitem>
2777
2778 <listitem>
2779 <!--
2780 Author: Heikki Linnakangas <[email protected]>
2781 Branch: master [ffd080d94] 2026-07-07 18:45:34 +0300
2782 Branch: REL_19_STABLE [eeb2940ae] 2026-07-07 18:46:10 +0300
2783 Branch: REL_18_STABLE [2167302b7] 2026-07-07 18:46:24 +0300
2784 Branch: REL_17_STABLE [c162810a5] 2026-07-07 18:46:58 +0300
2785 Branch: REL_16_STABLE [d3f329656] 2026-07-07 18:47:07 +0300
2786 Branch: REL_15_STABLE [4ecba7fa3] 2026-07-07 18:53:51 +0300
2787 Branch: REL_14_STABLE [1b018b5d1] 2026-07-07 18:54:09 +0300
2788 Branch: master [343594a26] 2026-07-07 18:45:37 +0300
2789 Branch: REL_19_STABLE [7f8745543] 2026-07-07 18:46:14 +0300
2790 Branch: REL_18_STABLE [bb0a54518] 2026-07-07 18:46:33 +0300
2791 Branch: REL_17_STABLE [177a2a2e3] 2026-07-07 18:46:58 +0300
2792 Branch: REL_16_STABLE [477bc27a5] 2026-07-07 18:47:07 +0300
2793 Branch: REL_15_STABLE [05908afcd] 2026-07-07 18:53:52 +0300
2794 Branch: REL_14_STABLE [d3888c90a] 2026-07-07 18:54:09 +0300
2795 Branch: master [d293f0345] 2026-07-09 18:34:24 +0300
2796 Branch: REL_19_STABLE [536512f34] 2026-07-09 18:34:53 +0300
2797 Branch: REL_18_STABLE [27761c015] 2026-07-09 18:35:12 +0300
2798 Branch: REL_17_STABLE [0958c3ea4] 2026-07-09 18:35:24 +0300
2799 Branch: REL_16_STABLE [6243ea6c3] 2026-07-09 18:35:37 +0300
2800 Branch: REL_15_STABLE [21a6c69ea] 2026-07-09 18:35:47 +0300
2801 Branch: REL_14_STABLE [f5f569713] 2026-07-09 18:36:30 +0300
2802 Branch: master [17accbe0f] 2026-07-09 18:34:27 +0300
2803 Branch: REL_19_STABLE [d9eb70c9c] 2026-07-09 18:34:53 +0300
2804 Branch: REL_18_STABLE [87c3a79ea] 2026-07-09 18:35:12 +0300
2805 Branch: REL_17_STABLE [bab0a2db7] 2026-07-09 18:35:24 +0300
2806 Branch: REL_16_STABLE [56988064b] 2026-07-09 18:35:37 +0300
2807 Branch: REL_15_STABLE [5ba13f8c0] 2026-07-09 18:36:18 +0300
2808 Branch: REL_14_STABLE [7532f2117] 2026-07-09 18:36:41 +0300
2809 -->
2810 <para>
2811 In <application>libpq</application>, always drain all pending bytes
2812 from the SSL or GSS decryption buffer
2813 during <function>pqReadData()</function> (Jacob Champion)
2814 <ulink url="&commit_baseurl;2167302b7">&sect;</ulink>
2815 <ulink url="&commit_baseurl;bb0a54518">&sect;</ulink>
2816 <ulink url="&commit_baseurl;27761c015">&sect;</ulink>
2817 <ulink url="&commit_baseurl;87c3a79ea">&sect;</ulink>
2818 </para>
2819
2820 <para>
2821 This avoids edge cases where <application>libpq</application> or its
2822 calling application waits for more data to arrive on the socket, but
2823 actually all the data has already arrived.
2824 </para>
2825 </listitem>
2826
2827 <listitem>
2828 <!--
2829 Author: Fujii Masao <[email protected]>
2830 Branch: master [676bf48e1] 2026-08-04 17:03:27 +0900
2831 Branch: REL_19_STABLE [8380013cd] 2026-08-04 17:05:37 +0900
2832 Branch: REL_18_STABLE [6b46a5d1b] 2026-08-04 17:05:44 +0900
2833 -->
2834 <para>
2835 Improve <application>libpq</application>'s handling of out-of-memory
2836 conditions (Anthonin Bonnefoy)
2837 <ulink url="&commit_baseurl;6b46a5d1b">&sect;</ulink>
2838 </para>
2839 </listitem>
2840
2841 <listitem>
2842 <!--
2843 Author: Heikki Linnakangas <[email protected]>
2844 Branch: master [b22b61905] 2026-07-03 14:57:35 +0300
2845 Branch: REL_19_STABLE [0766bc57e] 2026-07-03 14:59:56 +0300
2846 Branch: REL_18_STABLE [dd5eca055] 2026-07-03 15:00:00 +0300
2847 -->
2848 <para>
2849 Fix <application>libpq</application>'s trace facility to print
2850 new-style BackendKeyData and CancelRequest messages correctly
2851 (Anthonin Bonnefoy)
2852 <ulink url="&commit_baseurl;dd5eca055">&sect;</ulink>
2853 </para>
2854 </listitem>
2855
2856 <listitem>
2857 <!--
2858 Author: Heikki Linnakangas <[email protected]>
2859 Branch: master Release: REL_19_BR [e0511883c] 2026-06-15 11:28:45 +0300
2860 Branch: REL_18_STABLE [b1ab4bc52] 2026-06-15 11:35:20 +0300
2861 Branch: REL_17_STABLE [e4183c667] 2026-06-15 11:35:41 +0300
2862 Branch: REL_16_STABLE [8d516d2b9] 2026-06-15 11:38:07 +0300
2863 Branch: REL_15_STABLE [0f63b74a4] 2026-06-15 11:38:30 +0300
2864 Branch: REL_14_STABLE [1b79c8d1a] 2026-06-15 11:38:40 +0300
2865 -->
2866 <para>
2867 Allow <application>libpq</application> to accept
2868 ParameterDescription messages exceeding 30000 bytes (Ning Sun)
2869 <ulink url="&commit_baseurl;b1ab4bc52">&sect;</ulink>
2870 </para>
2871
2872 <para>
2873 Previously, this message type was not among those
2874 that <application>libpq</application>'s validity heuristics believed
2875 could be long. The limit resulted in failure for prepared queries
2876 having more than 7498 parameters, which is unlikely but supported.
2877 </para>
2878 </listitem>
2879
2880 <listitem>
2881 <!--
2882 Author: Tom Lane <[email protected]>
2883 Branch: master Release: REL_19_BR [7f5e0b22e] 2026-06-25 16:58:29 -0400
2884 Branch: REL_18_STABLE [917fdbc63] 2026-06-25 16:58:29 -0400
2885 -->
2886 <para>
2887 Fix null-pointer crash in <application>ecpg</application> compiler
2888 (Jehan-Guillaume de Rorthais)
2889 <ulink url="&commit_baseurl;917fdbc63">&sect;</ulink>
2890 </para>
2891
2892 <para>
2893 <application>ecpg</application> failed on
2894 a <literal>DECLARE</literal> section containing a union nested
2895 inside a struct.
2896 </para>
2897 </listitem>
2898
2899 <listitem>
2900 <!--
2901 Author: Fujii Masao <[email protected]>
2902 Branch: master Release: REL_19_BR [4484165b0] 2026-06-08 17:09:46 +0900
2903 Branch: REL_18_STABLE [081434b0f] 2026-06-08 17:10:25 +0900
2904 Branch: REL_17_STABLE [fe8c0a762] 2026-06-08 17:11:12 +0900
2905 Branch: REL_16_STABLE [4d4b73cfd] 2026-06-08 17:14:10 +0900
2906 Branch: REL_15_STABLE [bfeddcf09] 2026-06-08 17:14:15 +0900
2907 Branch: REL_14_STABLE [9e8fd9f7a] 2026-06-08 17:14:20 +0900
2908 -->
2909 <para>
2910 Reject multiple descriptor header items
2911 in <application>ecpg</application>'s <literal>GET/SET
2912 DESCRIPTOR</literal> statements (Masashi Kamura)
2913 <ulink url="&commit_baseurl;081434b0f">&sect;</ulink>
2914 </para>
2915
2916 <para>
2917 Previously the grammar allowed this syntax, but broken C code was
2918 generated. Adjust the grammar and the documentation to allow only
2919 one header item.
2920 </para>
2921 </listitem>
2922
2923 <listitem>
2924 <!--
2925 Author: Michael Paquier <[email protected]>
2926 Branch: master Release: REL_19_BR [d21604e17] 2026-06-03 08:58:26 +0900
2927 Branch: REL_18_STABLE [1e9bc4074] 2026-06-03 08:58:29 +0900
2928 -->
2929 <para>
2930 Fix issues with deferred errors in pipeline mode
2931 in <application>psql</application> (Michael Paquier)
2932 <ulink url="&commit_baseurl;1e9bc4074">&sect;</ulink>
2933 </para>
2934
2935 <para>
2936 <application>psql</application> could get stuck or suffer an
2937 assertion failure in some scenarios where the server reports an
2938 error in response to a Sync message, such as a deferred constraint
2939 violation.
2940 </para>
2941 </listitem>
2942
2943 <listitem>
2944 <!--
2945 Author: Michael Paquier <[email protected]>
2946 Branch: master Release: REL_19_BR [3d0d6741d] 2026-06-08 14:37:51 +0900
2947 Branch: REL_18_STABLE [07a6c262b] 2026-06-08 14:37:56 +0900
2948 Branch: REL_17_STABLE [efd885d05] 2026-06-08 14:37:57 +0900
2949 Branch: REL_16_STABLE [1edbe6695] 2026-06-08 14:37:59 +0900
2950 Branch: REL_15_STABLE [022ba5c61] 2026-06-08 14:38:00 +0900
2951 Branch: REL_14_STABLE [a4ca91ea1] 2026-06-08 14:38:01 +0900
2952 -->
2953 <para>
2954 Make line widths match in <application>psql</application>'s expanded
2955 aligned output format (Pavel Stehule)
2956 <ulink url="&commit_baseurl;07a6c262b">&sect;</ulink>
2957 </para>
2958
2959 <para>
2960 When the table's data rows are narrower than the record header lines,
2961 widen the data rows to match the headers, avoiding unsightly output.
2962 </para>
2963 </listitem>
2964
2965 <listitem>
2966 <!--
2967 Author: Daniel Gustafsson <[email protected]>
2968 Branch: master Release: REL_19_BR [e04910a9a] 2026-05-18 08:33:36 -0700
2969 Branch: REL_18_STABLE [e0c641ebb] 2026-05-18 08:33:36 -0700
2970 -->
2971 <para>
2972 Enforce the intended upper limit
2973 for <application>psql</application>'s special
2974 variable <varname>WATCH_INTERVAL</varname>
2975 (Sven Klemm, Daniel Gustafsson)
2976 <ulink url="&commit_baseurl;e0c641ebb">&sect;</ulink>
2977 </para>
2978
2979 <para>
2980 If a too-large value was given, <application>psql</application>
2981 reported an error but applied the setting anyway.
2982 </para>
2983 </listitem>
2984
2985 <listitem>
2986 <!--
2987 Author: Fujii Masao <[email protected]>
2988 Branch: master [38afc3dcb] 2026-07-25 19:08:27 +0900
2989 Branch: REL_19_STABLE [77aeca802] 2026-07-25 19:09:19 +0900
2990 Branch: REL_18_STABLE [f2d6cf880] 2026-07-25 19:10:15 +0900
2991 Branch: REL_17_STABLE [41949c6f3] 2026-07-25 19:10:22 +0900
2992 Branch: REL_16_STABLE [844bc718a] 2026-07-25 19:10:28 +0900
2993 Branch: REL_15_STABLE [e6e8a3078] 2026-07-25 19:10:49 +0900
2994 Branch: REL_14_STABLE [4e19081da] 2026-07-25 19:11:34 +0900
2995 -->
2996 <para>
2997 Fix <application>psql</application>'s privilege check for showing
2998 database size in <command>\l+</command> (Christoph Berg)
2999 <ulink url="&commit_baseurl;f2d6cf880">&sect;</ulink>
3000 </para>
3001
3002 <para>
3003 The underlying server function permits users who
3004 have <literal>pg_read_all_stats</literal> privileges to see the
3005 sizes of all databases, even if they lack <literal>CONNECT</literal>
3006 privilege. But <application>psql</application> was unaware of that
3007 provision and would not call the function unless the user
3008 has <literal>CONNECT</literal> privilege.
3009 </para>
3010 </listitem>
3011
3012 <listitem>
3013 <!--
3014 Author: Fujii Masao <[email protected]>
3015 Branch: master [6d4ca6de9] 2026-07-03 13:48:59 +0900
3016 Branch: REL_19_STABLE [558e0de6d] 2026-07-03 13:50:01 +0900
3017 Branch: REL_18_STABLE [598af79b1] 2026-07-03 13:50:08 +0900
3018 Branch: REL_17_STABLE [355a4fcf9] 2026-07-03 13:50:15 +0900
3019 Branch: REL_16_STABLE [f9afdb6d1] 2026-07-03 13:50:20 +0900
3020 Branch: REL_15_STABLE [c25737c89] 2026-07-03 13:50:26 +0900
3021 Branch: REL_14_STABLE [2d44bb900] 2026-07-03 13:50:51 +0900
3022 -->
3023 <para>
3024 Fix <application>psql</application>'s tab completion
3025 for <command>\df</command> to consider procedures too
3026 (Erik Wienhold)
3027 <ulink url="&commit_baseurl;598af79b1">&sect;</ulink>
3028 </para>
3029 </listitem>
3030
3031 <listitem>
3032 <!--
3033 Author: Fujii Masao <[email protected]>
3034 Branch: master Release: REL_19_BR [61f8a85a5] 2026-05-14 12:30:34 +0900
3035 Branch: REL_18_STABLE [98dd6c204] 2026-05-14 12:31:14 +0900
3036 Branch: REL_17_STABLE [52b3e7001] 2026-05-14 12:31:19 +0900
3037 Branch: REL_16_STABLE [6432a4cd6] 2026-05-14 12:31:25 +0900
3038 Branch: REL_15_STABLE [f18fcd9a4] 2026-05-14 12:31:43 +0900
3039 -->
3040 <para>
3041 Fix thread-safety bug in <application>pgbench</application>
3042 (Fujii Masao)
3043 <ulink url="&commit_baseurl;98dd6c204">&sect;</ulink>
3044 </para>
3045
3046 <para>
3047 When <application>pgbench</application> runs with multiple threads
3048 and the <option>--verbose-errors</option> option, different threads
3049 could attempt to use the same buffer to construct error messages,
3050 leading to corrupted log output.
3051 </para>
3052 </listitem>
3053
3054 <listitem>
3055 <!--
3056 Author: Peter Eisentraut <[email protected]>
3057 Branch: master Release: REL_19_BR [994f770a0] 2026-06-29 12:29:21 +0200
3058 Branch: REL_18_STABLE [d36b72894] 2026-06-29 13:01:57 +0200
3059 Branch: REL_17_STABLE [090ce6934] 2026-06-29 13:02:07 +0200
3060 -->
3061 <para>
3062 In <application>pg_combinebackup</application>, prevent infinite
3063 loop if the source file is shorter than expected (Peter Eisentraut)
3064 <ulink url="&commit_baseurl;d36b72894">&sect;</ulink>
3065 </para>
3066 </listitem>
3067
3068 <listitem>
3069 <!--
3070 Author: Fujii Masao <[email protected]>
3071 Branch: master Release: REL_19_BR [12d000488] 2026-05-27 10:34:17 +0900
3072 Branch: REL_18_STABLE [196b4b5ae] 2026-05-27 10:35:18 +0900
3073 Branch: REL_17_STABLE [c03784a21] 2026-05-27 10:35:49 +0900
3074 -->
3075 <para>
3076 Fix cleanup of publisher-side objects after errors
3077 in <application>pg_createsubscriber</application> (Nisha Moond)
3078 <ulink url="&commit_baseurl;196b4b5ae">&sect;</ulink>
3079 </para>
3080
3081 <para>
3082 When <application>pg_createsubscriber</application> fails after
3083 creating logical replication objects, it should remove the
3084 publication and replication slot that it created on the publisher.
3085 Some error cases failed to do so.
3086 </para>
3087 </listitem>
3088
3089 <listitem>
3090 <!--
3091 Author: Fujii Masao <[email protected]>
3092 Branch: master Release: REL_19_BR [263d1e6df] 2026-05-20 15:54:13 +0900
3093 Branch: REL_18_STABLE [89b4b3ae3] 2026-05-20 15:56:58 +0900
3094 Branch: REL_17_STABLE [ddd12d1a5] 2026-05-20 15:57:04 +0900
3095 Branch: REL_16_STABLE [9590dcfca] 2026-05-20 15:57:09 +0900
3096 Branch: REL_15_STABLE [ba9833a75] 2026-05-20 15:57:14 +0900
3097 Branch: REL_14_STABLE [5552a15a3] 2026-05-20 15:57:19 +0900
3098 -->
3099 <para>
3100 Use the source cluster's group-read file permissions
3101 for <application>pg_recvlogical</application> output files
3102 (Fujii Masao)
3103 <ulink url="&commit_baseurl;89b4b3ae3">&sect;</ulink>
3104 </para>
3105
3106 <para>
3107 <application>pg_recvlogical</application> was documented to behave
3108 this way, but it never actually enabled group-read.
3109 </para>
3110 </listitem>
3111
3112 <listitem>
3113 <!--
3114 Author: Michael Paquier <[email protected]>
3115 Branch: master Release: REL_19_BR [0dd93de69] 2026-06-16 08:21:08 +0900
3116 Branch: REL_18_STABLE [42ffdedcf] 2026-06-16 08:22:41 +0900
3117 Branch: master Release: REL_19_BR [ae39bd23c] 2026-06-16 15:58:12 +0900
3118 Branch: REL_18_STABLE [477efef08] 2026-06-16 15:58:17 +0900
3119 -->
3120 <para>
3121 Fix inconsistent behavior of <application>pg_restore</application>
3122 with <option>--statistics</option>
3123 or <option>--statistics-only</option>
3124 (Chao Li, Michael Paquier)
3125 <ulink url="&commit_baseurl;42ffdedcf">&sect;</ulink>
3126 <ulink url="&commit_baseurl;477efef08">&sect;</ulink>
3127 </para>
3128
3129 <para>
3130 When combined with other selective-restore options such
3131 as <option>--schema</option>, these options failed to restore the
3132 expected items, unlike <application>pg_dump</application> with
3133 similar options.
3134 </para>
3135 </listitem>
3136
3137 <listitem>
3138 <!--
3139 Author: Nathan Bossart <[email protected]>
3140 Branch: master Release: REL_19_BR [d2cea6306] 2026-06-17 09:18:39 -0500
3141 Branch: REL_18_STABLE [7e085aabd] 2026-06-17 09:18:39 -0500
3142 -->
3143 <para>
3144 Fix <command>vacuumdb --missing-stats-only</command> to ignore
3145 partitioned expression indexes (Baji Shaik)
3146 <ulink url="&commit_baseurl;7e085aabd">&sect;</ulink>
3147 </para>
3148
3149 <para>
3150 Previously, <application>vacuumdb</application> would always attempt
3151 to <command>ANALYZE</command> the partitioned table, accomplishing
3152 nothing since statistics are never created for partitioned indexes,
3153 only for their leaf indexes.
3154 </para>
3155 </listitem>
3156
3157 <listitem>
3158 <!--
3159 Author: Fujii Masao <[email protected]>
3160 Branch: master Release: REL_19_BR [389bd4c5b] 2026-06-12 09:37:37 +0900
3161 Branch: REL_18_STABLE [12c32bbc8] 2026-06-12 09:39:19 +0900
3162 -->
3163 <para>
3164 In <filename>contrib/amcheck</filename>, fix failure to report
3165 corruption of a btree metapage's <literal>allequalimage</literal>
3166 flag (Chao Li)
3167 <ulink url="&commit_baseurl;12c32bbc8">&sect;</ulink>
3168 </para>
3169 </listitem>
3170
3171 <listitem>
3172 <!--
3173 Author: Michael Paquier <[email protected]>
3174 Branch: master [e939332c6] 2026-07-06 09:32:25 +0900
3175 Branch: REL_19_STABLE [80cfd8aef] 2026-07-06 09:32:28 +0900
3176 Branch: REL_18_STABLE [1f8ab91c1] 2026-07-06 09:32:30 +0900
3177 -->
3178 <para>
3179 In <filename>contrib/amcheck</filename>, fix query-lifespan memory
3180 leak while verifying a GIN index (Kirill Reshke)
3181 <ulink url="&commit_baseurl;1f8ab91c1">&sect;</ulink>
3182 </para>
3183 </listitem>
3184
3185 <listitem>
3186 <!--
3187 Author: Alexander Korotkov <[email protected]>
3188 Branch: master Release: REL_19_BR [da1eff08a] 2026-06-14 04:04:48 +0300
3189 Branch: REL_18_STABLE [897e79486] 2026-06-14 04:05:50 +0300
3190 Branch: REL_17_STABLE [8abb8a155] 2026-06-14 04:07:00 +0300
3191 Branch: REL_16_STABLE [c89a1ca01] 2026-06-14 04:07:42 +0300
3192 Branch: REL_15_STABLE [4284476c0] 2026-06-14 04:08:00 +0300
3193 Branch: REL_14_STABLE [af09b18cb] 2026-06-14 04:06:43 +0300
3194 -->
3195 <para>
3196 In <filename>contrib/amcheck</filename>, handle short-header varlena
3197 datums correctly (Andrey Borodin)
3198 <ulink url="&commit_baseurl;897e79486">&sect;</ulink>
3199 </para>
3200
3201 <para>
3202 This error could result in doing excess work while verifying a btree
3203 index, but seems not to have had any worse consequences.
3204 </para>
3205 </listitem>
3206
3207 <listitem>
3208 <!--
3209 Author: Tom Lane <[email protected]>
3210 Branch: master [7d3448961] 2026-07-01 13:27:22 -0400
3211 Branch: REL_19_STABLE [a47005f0b] 2026-07-01 13:27:22 -0400
3212 Branch: REL_18_STABLE [1e1d07792] 2026-07-01 13:27:22 -0400
3213 Branch: REL_17_STABLE [d215d2cc2] 2026-07-01 13:27:22 -0400
3214 Branch: REL_16_STABLE [d569ccd40] 2026-07-01 13:27:22 -0400
3215 Branch: REL_15_STABLE [98dd4406f] 2026-07-01 13:27:22 -0400
3216 Branch: REL_14_STABLE [255bce448] 2026-07-01 13:27:22 -0400
3217 -->
3218 <para>
3219 In <filename>contrib/btree_gist</filename>,
3220 fix <literal>NaN</literal> handling in the <type>float4</type>
3221 and <type>float8</type> opclasses (Bill Kim, Tom Lane)
3222 <ulink url="&commit_baseurl;1e1d07792">&sect;</ulink>
3223 </para>
3224
3225 <para>
3226 Comparisons, as well as the GiST penalty and distance functions, did
3227 not account for <literal>NaN</literal> and would give the wrong
3228 answer when handed one. It is recommended to
3229 reindex <filename>btree_gist</filename> indexes on float columns
3230 after installing this update, if there is any possibility that there
3231 are <literal>NaN</literal> entries in those columns.
3232 </para>
3233 </listitem>
3234
3235 <listitem>
3236 <!--
3237 Author: Tom Lane <[email protected]>
3238 Branch: master [a9fa6c69e] 2026-07-03 13:11:14 -0400
3239 Branch: REL_19_STABLE [11cb9c431] 2026-07-03 13:11:14 -0400
3240 Branch: REL_18_STABLE [558c4ea9a] 2026-07-03 13:11:14 -0400
3241 -->
3242 <para>
3243 In <filename>contrib/btree_gist</filename>, fix sorting
3244 of <type>bit</type>/<type>varbit</type> entries during GiST index
3245 construction (Tom Lane)
3246 <ulink url="&commit_baseurl;558c4ea9a">&sect;</ulink>
3247 </para>
3248
3249 <para>
3250 Values of bit types were sorted as though they
3251 were <type>bytea</type>s, which did not cause any obvious failure
3252 but would result in an inefficient index, since the types'
3253 representations are different. It is recommended to
3254 reindex <filename>btree_gist</filename> indexes on bit columns
3255 after installing this update.
3256 </para>
3257 </listitem>
3258
3259 <listitem>
3260 <!--
3261 Author: Tom Lane <[email protected]>
3262 Branch: master [eef644e57] 2026-07-03 13:50:14 -0400
3263 Branch: REL_19_STABLE [fc6649abe] 2026-07-03 13:50:14 -0400
3264 Branch: REL_18_STABLE [12c519207] 2026-07-03 13:50:14 -0400
3265 Branch: REL_17_STABLE [86992769e] 2026-07-03 13:50:14 -0400
3266 Branch: REL_16_STABLE [0663382c9] 2026-07-03 13:50:14 -0400
3267 Branch: REL_15_STABLE [8f2a1b3d3] 2026-07-03 13:50:14 -0400
3268 Branch: REL_14_STABLE [286f9a3ce] 2026-07-03 13:50:14 -0400
3269 -->
3270 <para>
3271 In <filename>contrib/btree_gist</filename>, fix searches using a
3272 not-equal operator (Ayush Tiwari)
3273 <ulink url="&commit_baseurl;12c519207">&sect;</ulink>
3274 </para>
3275
3276 <para>
3277 For variable-length data types, the code for scanning non-leaf index
3278 pages applied the wrong comparison function, leading to wrong
3279 results and potentially crashes.
3280 </para>
3281 </listitem>
3282
3283 <listitem>
3284 <!--
3285 Author: Fujii Masao <[email protected]>
3286 Branch: master Release: REL_19_BR [97f6fc10f] 2026-05-26 00:46:31 +0900
3287 Branch: REL_18_STABLE [88d7748d2] 2026-05-26 00:47:43 +0900
3288 Branch: master Release: REL_19_BR [5f5165e2f] 2026-05-26 00:51:18 +0900
3289 Branch: REL_18_STABLE [130396e6c] 2026-05-26 00:52:38 +0900
3290 -->
3291 <para>
3292 In <filename>contrib/dblink</filename>
3293 and <filename>contrib/postgres_fdw</filename>, ensure that a user-mapping
3294 setting for <varname>use_scram_passthrough</varname> overrides one
3295 for a foreign server (Matheus Alcantara)
3296 <ulink url="&commit_baseurl;88d7748d2">&sect;</ulink>
3297 <ulink url="&commit_baseurl;130396e6c">&sect;</ulink>
3298 </para>
3299
3300 <para>
3301 Previously the precedence went the other way, but that is
3302 inconsistent with the behavior of other foreign-table options.
3303 </para>
3304 </listitem>
3305
3306 <listitem>
3307 <!--
3308 Author: Fujii Masao <[email protected]>
3309 Branch: master Release: REL_19_BR [e2b881340] 2026-05-26 01:07:24 +0900
3310 Branch: REL_18_STABLE [cd777e27e] 2026-05-26 01:08:47 +0900
3311 -->
3312 <para>
3313 Reject setting <varname>use_scram_passthrough</varname>
3314 on <filename>contrib/dblink</filename> foreign-data wrappers
3315 (Matheus Alcantara)
3316 <ulink url="&commit_baseurl;cd777e27e">&sect;</ulink>
3317 </para>
3318
3319 <para>
3320 This option is only meaningful on foreign servers and user
3321 mappings, but dblink incorrectly allowed it at the FDW level as
3322 well (and then ignored it).
3323 </para>
3324 </listitem>
3325
3326 <listitem>
3327 <!--
3328 Author: Tom Lane <[email protected]>
3329 Branch: master Release: REL_19_BR [da82fbb8f] 2026-06-17 11:04:41 -0400
3330 Branch: REL_18_STABLE [e3b7a43fa] 2026-06-17 11:04:41 -0400
3331 Branch: REL_17_STABLE [3df0b7755] 2026-06-17 11:04:41 -0400
3332 Branch: REL_16_STABLE [b0f3465b6] 2026-06-17 11:04:41 -0400
3333 Branch: REL_15_STABLE [a6f23c3ad] 2026-06-17 11:04:41 -0400
3334 Branch: REL_14_STABLE [639fff511] 2026-06-17 11:04:41 -0400
3335 Branch: master Release: REL_19_BR [c0f17b04d] 2026-06-18 12:23:13 -0400
3336 Branch: REL_18_STABLE [d65cf6f80] 2026-06-18 12:22:55 -0400
3337 Branch: REL_17_STABLE [4efef9d18] 2026-06-18 12:22:55 -0400
3338 Branch: REL_16_STABLE [60a1d712a] 2026-06-18 12:22:55 -0400
3339 Branch: REL_15_STABLE [4fbbabb0a] 2026-06-18 12:22:55 -0400
3340 Branch: REL_14_STABLE [1f6b2295f] 2026-06-18 12:22:55 -0400
3341 -->
3342 <para>
3343 Fix unguarded recursion and loops in
3344 <filename>contrib/hstore_plperl</filename>,
3345 <filename>contrib/jsonb_plperl</filename>, and
3346 <filename>contrib/jsonb_plpython</filename>
3347 (Aleksander Alekseev)
3348 <ulink url="&commit_baseurl;e3b7a43fa">&sect;</ulink>
3349 <ulink url="&commit_baseurl;d65cf6f80">&sect;</ulink>
3350 </para>
3351
3352 <para>
3353 Prevent stack overflow when dealing with deeply
3354 nested <type>jsonb</type> values, and allow interruption of the infinite
3355 loop caused when attempting to dereference circular chains of Perl
3356 object references.
3357 </para>
3358 </listitem>
3359
3360 <listitem>
3361 <!--
3362 Author: Tom Lane <[email protected]>
3363 Branch: master Release: REL_19_BR [524cc0f63] 2026-05-25 18:15:49 -0400
3364 Branch: REL_18_STABLE [e7544c518] 2026-05-25 18:15:49 -0400
3365 Branch: REL_17_STABLE [94b57ab54] 2026-05-25 18:15:49 -0400
3366 Branch: REL_16_STABLE [273be484a] 2026-05-25 18:15:49 -0400
3367 Branch: REL_15_STABLE [702a6d5f6] 2026-05-25 18:15:49 -0400
3368 Branch: REL_14_STABLE [a96b051a9] 2026-05-25 18:15:49 -0400
3369 -->
3370 <para>
3371 Fix missed release of statistics catcache entry
3372 in <filename>contrib/intarray</filename> (Man Zeng)
3373 <ulink url="&commit_baseurl;e7544c518">&sect;</ulink>
3374 </para>
3375
3376 <para>
3377 This oversight led to warnings like <quote>resource was not closed:
3378 cache pg_statistic</quote>.
3379 </para>
3380 </listitem>
3381
3382 <listitem>
3383 <!--
3384 Author: Heikki Linnakangas <[email protected]>
3385 Branch: master Release: REL_19_BR [3f3280491] 2026-06-16 09:29:47 +0300
3386 Branch: REL_18_STABLE [c3e36a9a5] 2026-06-16 09:31:08 +0300
3387 Branch: REL_17_STABLE [c391c00d9] 2026-06-16 09:31:12 +0300
3388 Branch: REL_16_STABLE [aca944e33] 2026-06-16 09:31:17 +0300
3389 Branch: REL_15_STABLE [1bec6b1c1] 2026-06-16 09:31:20 +0300
3390 Branch: REL_14_STABLE [f528a5606] 2026-06-16 09:31:23 +0300
3391 -->
3392 <para>
3393 In <filename>contrib/ltree</filename>, fix integer overflow in
3394 comparisons (Ayush Tiwari)
3395 <ulink url="&commit_baseurl;c3e36a9a5">&sect;</ulink>
3396 </para>
3397
3398 <para>
3399 <type>ltree</type> values containing more than about 14,653 labels
3400 resulted in wrong comparison answers due to overflow. If a btree
3401 index contains such values, it is probably corrupt and should be
3402 reindexed after installing this update.
3403 </para>
3404 </listitem>
3405
3406 <listitem>
3407 <!--
3408 Author: Tom Lane <[email protected]>
3409 Branch: master Release: REL_19_BR [80bb0ebcc] 2026-06-22 12:59:16 -0400
3410 Branch: REL_18_STABLE [020426268] 2026-06-22 12:59:16 -0400
3411 Branch: REL_17_STABLE [2aa6be6e6] 2026-06-22 12:59:16 -0400
3412 -->
3413 <para>
3414 In <filename>contrib/pgcrypto</filename>, avoid double-free crash
3415 after encountering an error while using an OSSLCipher object
3416 (Yuelin Wang)
3417 <ulink url="&commit_baseurl;020426268">&sect;</ulink>
3418 </para>
3419 </listitem>
3420
3421 <listitem>
3422 <!--
3423 Author: Tomas Vondra <[email protected]>
3424 Branch: master Release: REL_19_BR [dac36601f] 2026-06-26 19:47:36 +0200
3425 Branch: REL_18_STABLE [3bf2cb225] 2026-06-26 19:48:20 +0200
3426 -->
3427 <para>
3428 Fix out-of-bounds access
3429 in <filename>contrib/pg_prewarm</filename>'s autoprewarm worker
3430 (Matheus Alcantara)
3431 <ulink url="&commit_baseurl;3bf2cb225">&sect;</ulink>
3432 </para>
3433
3434 <para>
3435 The code tried to fetch a value from one past the end of an array,
3436 risking a segfault.
3437 </para>
3438 </listitem>
3439
3440 <listitem>
3441 <!--
3442 Author: Michael Paquier <[email protected]>
3443 Branch: master Release: REL_19_BR [193a4ded9] 2026-06-06 08:16:36 +0900
3444 Branch: REL_18_STABLE [2b09f8a91] 2026-06-06 08:16:40 +0900
3445 Branch: REL_17_STABLE [0bcf19c9e] 2026-06-06 08:16:41 +0900
3446 Branch: REL_16_STABLE [daf8bc7d4] 2026-06-06 08:16:43 +0900
3447 Branch: REL_15_STABLE [51f63ba2b] 2026-06-06 08:16:44 +0900
3448 Branch: REL_14_STABLE [1eda3eb07] 2026-06-06 08:16:46 +0900
3449 -->
3450 <para>
3451 Fix array overrun in <filename>contrib/pg_surgery</filename>'s
3452 <function>heap_force_kill</function> and
3453 <function>heap_force_freeze</function> functions (Michael Paquier)
3454 <ulink url="&commit_baseurl;2b09f8a91">&sect;</ulink>
3455 </para>
3456
3457 <para>
3458 Attempting to change a TID whose offset number equals
3459 MaxHeapTuplesPerPage wrote one byte past the end of the allocated
3460 array, potentially crashing the server.
3461 </para>
3462 </listitem>
3463
3464 <listitem>
3465 <!--
3466 Author: Álvaro Herrera <[email protected]>
3467 Branch: master [346fbdcc2] 2026-08-04 11:44:11 +0200
3468 Branch: REL_19_STABLE [1f24c8237] 2026-08-04 11:44:11 +0200
3469 Branch: REL_18_STABLE [19f0391df] 2026-08-04 11:44:11 +0200
3470 Branch: REL_17_STABLE [1b6c99d96] 2026-08-04 11:44:11 +0200
3471 Branch: REL_16_STABLE [eb28b6f24] 2026-08-04 11:44:11 +0200
3472 Branch: REL_15_STABLE [395700f48] 2026-08-04 11:44:11 +0200
3473 Branch: REL_14_STABLE [e9d53cf45] 2026-08-04 11:44:11 +0200
3474 -->
3475 <para>
3476 In <filename>contrib/pg_surgery</filename>, avoid infinite loop with
3477 TID arrays having more than 64K elements (Andrey Rachitskiy)
3478 <ulink url="&commit_baseurl;19f0391df">&sect;</ulink>
3479 </para>
3480 </listitem>
3481
3482 <listitem>
3483 <!--
3484 Author: Nathan Bossart <[email protected]>
3485 Branch: master Release: REL_19_BR [611756948] 2026-05-14 13:11:49 -0500
3486 Branch: REL_18_STABLE [ed0c4d5af] 2026-05-14 13:11:49 -0500
3487 Branch: REL_17_STABLE [6b4de201e] 2026-05-14 13:11:49 -0500
3488 Branch: REL_16_STABLE [eb93f10e2] 2026-05-14 13:11:49 -0500
3489 Branch: REL_15_STABLE [77b2d18e9] 2026-05-14 13:11:49 -0500
3490 Branch: REL_14_STABLE [1de0a711d] 2026-05-14 13:11:49 -0500
3491 -->
3492 <para>
3493 Avoid NULL-pointer dereference
3494 in <filename>contrib/refint</filename>'s
3495 <function>check_foreign_key()</function> (Ayush Tiwari)
3496 <ulink url="&commit_baseurl;ed0c4d5af">&sect;</ulink>
3497 </para>
3498
3499 <para>
3500 In the on-update-cascade case, a null value of a referenced column
3501 led to a crash. This is an oversight in the fix for CVE-2026-6637,
3502 but the code that was there before that wasn't really right either.
3503 </para>
3504 </listitem>
3505
3506 <listitem>
3507 <!--
3508 Author: Heikki Linnakangas <[email protected]>
3509 Branch: master Release: REL_19_BR [0e1f1ed15] 2026-06-11 12:33:48 +0300
3510 Branch: REL_18_STABLE [0004cab4d] 2026-06-11 12:34:26 +0300
3511 Branch: REL_17_STABLE [bcbbd070d] 2026-06-11 12:34:32 +0300
3512 Branch: REL_16_STABLE [504ca0513] 2026-06-11 12:34:37 +0300
3513 Branch: REL_15_STABLE [b3aa2083a] 2026-06-11 12:34:42 +0300
3514 Branch: REL_14_STABLE [58b91fc73] 2026-06-11 12:34:45 +0300
3515 -->
3516 <para>
3517 Fix <filename>contrib/seg</filename> to print segments
3518 with <literal>~</literal> certainty indicators correctly
3519 (Ewan Young)
3520 <ulink url="&commit_baseurl;0004cab4d">&sect;</ulink>
3521 </para>
3522
3523 <para>
3524 Due to a typo, <function>seg_out()</function> did not print
3525 a <literal>~</literal> certainty indicator attached to a segment's
3526 upper boundary. Worse, if the lower boundary
3527 had <literal>~</literal> while the upper boundary had no indicator,
3528 the upper boundary was not printed at all, incorrectly converting
3529 the value into an open interval.
3530 </para>
3531 </listitem>
3532
3533 <listitem>
3534 <!--
3535 Author: Michael Paquier <[email protected]>
3536 Branch: master Release: REL_19_BR [9d33a5a80] 2026-06-11 14:29:18 +0900
3537 Branch: REL_18_STABLE [91b57eade] 2026-06-11 14:29:22 +0900
3538 Branch: REL_17_STABLE [4a49ab289] 2026-06-11 14:29:24 +0900
3539 Branch: REL_16_STABLE [18955d412] 2026-06-11 14:29:26 +0900
3540 Branch: REL_15_STABLE [bc5775149] 2026-06-11 14:29:28 +0900
3541 Branch: REL_14_STABLE [f3f901a53] 2026-06-11 14:29:29 +0900
3542 -->
3543 <para>
3544 Fix crash with namespace nodes in <filename>contrib/xml2</filename>'s
3545 <function>xpath_nodeset()</function> function (Andrey Chernyy,
3546 Michael Paquier)
3547 <ulink url="&commit_baseurl;91b57eade">&sect;</ulink>
3548 </para>
3549 </listitem>
3550
3551 <listitem>
3552 <!--
3553 Author: Daniel Gustafsson <[email protected]>
3554 Branch: master Release: REL_19_BR [89d243d52] 2026-05-29 21:52:35 +0200
3555 Branch: REL_18_STABLE [27cf3b5af] 2026-06-12 13:57:22 +0200
3556 Branch: REL_17_STABLE [8bcabfcce] 2026-06-12 13:57:22 +0200
3557 Branch: REL_16_STABLE [fb8befa7b] 2026-06-12 13:57:22 +0200
3558 Branch: REL_15_STABLE [c7f70fa1b] 2026-06-12 13:57:22 +0200
3559 Branch: REL_14_STABLE [086652c02] 2026-06-12 13:57:22 +0200
3560 -->
3561 <para>
3562 Support building <productname>PostgreSQL</productname> with
3563 OpenSSL 4 (Daniel Gustafsson)
3564 <ulink url="&commit_baseurl;27cf3b5af">&sect;</ulink>
3565 </para>
3566 </listitem>
3567
3568 <listitem>
3569 <!--
3570 Author: Tom Lane <[email protected]>
3571 Branch: master [6ca405938] 2026-08-02 11:26:30 -0400
3572 Branch: REL_19_STABLE [3c16aa293] 2026-08-02 11:26:30 -0400
3573 Branch: REL_18_STABLE [5f67124fa] 2026-08-02 11:26:30 -0400
3574 Branch: REL_17_STABLE [669438aed] 2026-08-02 11:26:30 -0400
3575 Branch: REL_16_STABLE [796c275a0] 2026-08-02 11:26:30 -0400
3576 Branch: REL_15_STABLE [af7be5672] 2026-08-02 11:26:30 -0400
3577 Branch: REL_14_STABLE [812cc1a73] 2026-08-02 11:26:30 -0400
3578 -->
3579 <para>
3580 Update time zone data files to <application>tzdata</application>
3581 release 2026c (Tom Lane)
3582 <ulink url="&commit_baseurl;5f67124fa">&sect;</ulink>
3583 </para>
3584
3585 <para>
3586 Alberta (America/Edmonton) will be on year-round UTC-06
3587 (effectively, permanent DST) beginning in November 2026. This
3588 release assumes that their TZ abbreviation will
3589 be <literal>CST</literal> from that time forward. That seems likely
3590 to change, but it's unclear what new abbreviation will be used.
3591 </para>
3592
3593 <para>
3594 Morocco (Africa/Casablanca) will move to permanent UTC+00,
3595 without daylight saving time transitions, on 2026-09-20.
3596 </para>
3597 </listitem>
3598
3599 </itemizedlist>
3600
3601 </sect2>
3602 </sect1>
3603
3604 <sect1 id="release-18-4">
3605 <title>Release 18.4</title>
3606
3607 <formalpara>
3608 <title>Release date:</title>
3609 <para>2026-05-14</para>
3610 </formalpara>
3611
3612 <para>
3613 This release contains a variety of fixes from 18.3.
3614 For information about new features in major release 18, see
3615 <xref linkend="release-18"/>.
3616 </para>
3617
3618 <sect2 id="release-18-4-migration">
3619 <title>Migration to Version 18.4</title>
3620
3621 <para>
3622 A dump/restore is not required for those running 18.X.
3623 </para>
3624
3625 <para>
3626 However, if you are upgrading from a version earlier than 18.2,
3627 see <xref linkend="release-18-2"/>.
3628 </para>
3629 </sect2>
3630
3631 <sect2 id="release-18-4-changes">
3632 <title>Changes</title>
3633
3634 <itemizedlist>
3635
3636 <listitem>
3637 <!--
3638 Author: Michael Paquier <[email protected]>
3639 Branch: master [b63f25bdd] 2026-05-11 05:13:46 -0700
3640 Branch: REL_18_STABLE [f7a191f53] 2026-05-11 05:13:47 -0700
3641 Branch: REL_17_STABLE [32a4ce55c] 2026-05-11 05:13:48 -0700
3642 Branch: REL_16_STABLE [66cf26b9e] 2026-05-11 05:13:49 -0700
3643 Branch: REL_15_STABLE [3fb66d302] 2026-05-11 05:13:50 -0700
3644 Branch: REL_14_STABLE [3b4e66739] 2026-05-11 05:13:51 -0700
3645 Branch: REL_17_STABLE [6dffaeb8e] 2026-05-11 05:13:48 -0700
3646 Branch: REL_16_STABLE [c2e6ef863] 2026-05-11 05:13:49 -0700
3647 Branch: REL_15_STABLE [16fda4df6] 2026-05-11 05:13:50 -0700
3648 Branch: REL_14_STABLE [14a4a7040] 2026-05-11 05:13:51 -0700
3649 -->
3650 <para>
3651 Prevent unbounded recursion while processing startup packets
3652 (Michael Paquier)
3653 <ulink url="&commit_baseurl;f7a191f53">&sect;</ulink>
3654 </para>
3655
3656 <para>
3657 A malicious client could crash the connected backend by alternating
3658 rejected SSL and GSS encryption requests indefinitely.
3659 </para>
3660
3661 <para>
3662 The <productname>PostgreSQL</productname> Project thanks Calif.io
3663 (in collaboration with Claude and Anthropic Research) for reporting
3664 this problem.
3665 (CVE-2026-6479)
3666 </para>
3667 </listitem>
3668
3669 <listitem>
3670 <!--
3671 Author: Tom Lane <[email protected]>
3672 Branch: master [46593aea0] 2026-05-11 05:13:46 -0700
3673 Branch: REL_18_STABLE [e1c30458a] 2026-05-11 05:13:47 -0700
3674 Branch: REL_17_STABLE [fe2720c45] 2026-05-11 05:13:48 -0700
3675 Branch: REL_16_STABLE [cfb610eaa] 2026-05-11 05:13:49 -0700
3676 Branch: REL_15_STABLE [bfc5cea76] 2026-05-11 05:13:50 -0700
3677 Branch: REL_14_STABLE [61a9b4b6e] 2026-05-11 05:13:51 -0700
3678 Author: Tom Lane <[email protected]>
3679 Branch: master [c55cea529] 2026-05-11 05:13:46 -0700
3680 Branch: REL_18_STABLE [01e568b8c] 2026-05-11 05:13:47 -0700
3681 Branch: REL_17_STABLE [01b5ef7df] 2026-05-11 05:13:48 -0700
3682 Branch: REL_16_STABLE [aff71f87b] 2026-05-11 05:13:49 -0700
3683 Branch: REL_15_STABLE [4032c9d98] 2026-05-11 05:13:50 -0700
3684 Branch: REL_14_STABLE [e31ef0720] 2026-05-11 05:13:51 -0700
3685 Author: Tom Lane <[email protected]>
3686 Branch: master [0dc1fdc75] 2026-05-11 05:13:46 -0700
3687 Branch: REL_18_STABLE [f3cee4dc4] 2026-05-11 05:13:47 -0700
3688 Branch: REL_17_STABLE [e3a2bea41] 2026-05-11 05:13:48 -0700
3689 Branch: REL_16_STABLE [a4f089c79] 2026-05-11 05:13:49 -0700
3690 Branch: REL_15_STABLE [7fdb0907e] 2026-05-11 05:13:50 -0700
3691 Branch: REL_14_STABLE [39bc8f2ca] 2026-05-11 05:13:51 -0700
3692 Author: Tom Lane <[email protected]>
3693 Branch: master [b2869ebc4] 2026-05-11 05:13:47 -0700
3694 Branch: REL_18_STABLE [dd8af778d] 2026-05-11 05:13:48 -0700
3695 Branch: REL_17_STABLE [26dd3cac2] 2026-05-11 05:13:49 -0700
3696 Branch: REL_16_STABLE [c25973124] 2026-05-11 05:13:50 -0700
3697 Branch: REL_15_STABLE [fb0bc321d] 2026-05-11 05:13:51 -0700
3698 Branch: REL_14_STABLE [bcfd848e7] 2026-05-11 05:13:51 -0700
3699 Author: Nathan Bossart <[email protected]>
3700 Branch: master [6a985e71e] 2026-05-11 05:13:47 -0700
3701 Branch: REL_18_STABLE [55328e3a9] 2026-05-11 05:13:48 -0700
3702 Branch: REL_17_STABLE [87357a606] 2026-05-11 05:13:49 -0700
3703 Branch: REL_16_STABLE [32c525eb6] 2026-05-11 05:13:50 -0700
3704 Branch: REL_15_STABLE [137013f60] 2026-05-11 05:13:50 -0700
3705 Branch: REL_14_STABLE [986753361] 2026-05-11 05:13:51 -0700
3706 Author: Heikki Linnakangas <[email protected]>
3707 Branch: master [6d68fcb28] 2026-05-11 05:13:47 -0700
3708 Branch: REL_18_STABLE [67dd6243d] 2026-05-11 05:13:48 -0700
3709 Branch: REL_17_STABLE [3c41f5534] 2026-05-11 05:13:49 -0700
3710 Branch: REL_16_STABLE [e24fb3247] 2026-05-11 05:13:50 -0700
3711 Branch: REL_15_STABLE [e49e9590d] 2026-05-11 05:13:51 -0700
3712 Branch: REL_14_STABLE [8e81995de] 2026-05-11 05:13:51 -0700
3713 Author: Tom Lane <[email protected]>
3714 Branch: master [066b7b144] 2026-05-11 05:13:46 -0700
3715 Branch: REL_18_STABLE [8d1489d50] 2026-05-11 05:13:47 -0700
3716 Branch: REL_17_STABLE [ebcfa7867] 2026-05-11 05:13:48 -0700
3717 Branch: REL_16_STABLE [f20b84081] 2026-05-11 05:13:49 -0700
3718 Branch: REL_15_STABLE [b11c3eadf] 2026-05-11 05:13:50 -0700
3719 Branch: REL_14_STABLE [3e0eba196] 2026-05-11 05:13:51 -0700
3720 Author: Tom Lane <[email protected]>
3721 Branch: REL_18_STABLE [c7fb9f765] 2026-05-11 05:13:47 -0700
3722 Branch: REL_17_STABLE [00e243e67] 2026-05-11 05:13:48 -0700
3723 Branch: REL_16_STABLE [924b3e943] 2026-05-11 05:13:49 -0700
3724 Branch: REL_15_STABLE [d75b1dc96] 2026-05-11 05:13:50 -0700
3725 Branch: REL_14_STABLE [37842f3dc] 2026-05-11 05:13:51 -0700
3726 Author: Tom Lane <[email protected]>
3727 Branch: REL_17_STABLE [e5babf754] 2026-05-11 05:13:48 -0700
3728 Branch: REL_16_STABLE [47dae5e74] 2026-05-11 05:13:49 -0700
3729 Branch: REL_15_STABLE [d106295b6] 2026-05-11 05:13:50 -0700
3730 Branch: REL_14_STABLE [6a423a256] 2026-05-11 05:13:51 -0700
3731 Author: Heikki Linnakangas <[email protected]>
3732 Branch: master [c3f7dde39] 2026-05-11 21:27:55 +0300
3733 Branch: REL_18_STABLE [3fbec9e50] 2026-05-11 21:28:46 +0300
3734 Branch: REL_17_STABLE [8e909812d] 2026-05-11 21:28:57 +0300
3735 Branch: REL_16_STABLE [e42598a41] 2026-05-11 21:29:08 +0300
3736 Branch: REL_15_STABLE [dc6c85ff4] 2026-05-11 21:29:18 +0300
3737 Branch: REL_14_STABLE [c9447b8bd] 2026-05-11 21:29:27 +0300
3738 -->
3739 <para>
3740 Fix assorted integer overflows in memory-allocation calculations
3741 (Tom Lane, Nathan Bossart, Heikki Linnakangas)
3742 <ulink url="&commit_baseurl;e1c30458a">&sect;</ulink>
3743 <ulink url="&commit_baseurl;01e568b8c">&sect;</ulink>
3744 <ulink url="&commit_baseurl;f3cee4dc4">&sect;</ulink>
3745 <ulink url="&commit_baseurl;dd8af778d">&sect;</ulink>
3746 <ulink url="&commit_baseurl;55328e3a9">&sect;</ulink>
3747 <ulink url="&commit_baseurl;67dd6243d">&sect;</ulink>
3748 <ulink url="&commit_baseurl;8d1489d50">&sect;</ulink>
3749 <ulink url="&commit_baseurl;c7fb9f765">&sect;</ulink>
3750 <ulink url="&commit_baseurl;3fbec9e50">&sect;</ulink>
3751 </para>
3752
3753 <para>
3754 Various places were incautious about the possibility of integer
3755 overflow in calculations of how much memory to allocate. Overflow
3756 would lead to allocating a too-small buffer which the caller would
3757 then write past the end of. This would at least trigger server
3758 crashes, and probably could be exploited for arbitrary code
3759 execution. In many but by no means all cases, the hazard exists
3760 only in 32-bit builds.
3761 </para>
3762
3763 <para>
3764 The <productname>PostgreSQL</productname> Project thanks Xint Code,
3765 Bruce Dang, Sven Klemm, and Pavel Kohout for reporting these problems.
3766 (CVE-2026-6473)
3767 </para>
3768 </listitem>
3769
3770 <listitem>
3771 <!--
3772 Author: Nathan Bossart <[email protected]>
3773 Branch: master [d389415ff] 2026-05-11 05:13:47 -0700
3774 Branch: REL_18_STABLE [c2e44c370] 2026-05-11 05:13:47 -0700
3775 Branch: REL_17_STABLE [d7de7fa84] 2026-05-11 05:13:49 -0700
3776 -->
3777 <para>
3778 Properly quote subscription names
3779 in <application>pg_createsubscriber</application> (Nathan Bossart)
3780 <ulink url="&commit_baseurl;c2e44c370">&sect;</ulink>
3781 </para>
3782
3783 <para>
3784 The given subscription name was inserted into SQL commands without
3785 quoting, so that SQL injection could be achieved in the (perhaps
3786 unlikely) case that the subscription name comes from an untrusted
3787 source.
3788 </para>
3789
3790 <para>
3791 The <productname>PostgreSQL</productname> Project thanks
3792 Yu Kunpeng for reporting this problem.
3793 (CVE-2026-6476)
3794 </para>
3795 </listitem>
3796
3797 <listitem>
3798 <!--
3799 Author: Noah Misch <[email protected]>
3800 Branch: master [46b4f5c11] 2026-05-11 05:13:46 -0700
3801 Branch: REL_18_STABLE [cb35d7306] 2026-05-11 05:13:47 -0700
3802 Branch: REL_17_STABLE [f0f59b658] 2026-05-11 05:13:48 -0700
3803 Branch: REL_16_STABLE [248a433cd] 2026-05-11 05:13:50 -0700
3804 -->
3805 <para>
3806 Properly quote object names in logical replication origin checks
3807 (Pavel Kohout)
3808 <ulink url="&commit_baseurl;cb35d7306">&sect;</ulink>
3809 </para>
3810
3811 <para>
3812 <command>ALTER SUBSCRIPTION ... REFRESH PUBLICATION</command>
3813 interpolated schema and relation names into SQL commands without
3814 quoting them, allowing execution of arbitrary SQL on the publisher.
3815 </para>
3816
3817 <para>
3818 The <productname>PostgreSQL</productname> Project thanks
3819 Pavel Kohout for reporting this problem.
3820 (CVE-2026-6638)
3821 </para>
3822 </listitem>
3823
3824 <listitem>
3825 <!--
3826 Author: Michael Paquier <[email protected]>
3827 Branch: master [d388e1d7f] 2026-05-11 05:13:46 -0700
3828 Branch: REL_18_STABLE [62ad26266] 2026-05-11 05:13:47 -0700
3829 Branch: REL_17_STABLE [3ed3dbbf4] 2026-05-11 05:13:48 -0700
3830 Branch: REL_16_STABLE [5919e0005] 2026-05-11 05:13:49 -0700
3831 Branch: REL_15_STABLE [7fe365693] 2026-05-11 05:13:50 -0700
3832 Branch: REL_14_STABLE [2d267ffc4] 2026-05-11 05:13:51 -0700
3833 -->
3834 <para>
3835 Reject over-length options in <function>ts_headline()</function>
3836 (Michael Paquier)
3837 <ulink url="&commit_baseurl;62ad26266">&sect;</ulink>
3838 </para>
3839
3840 <para>
3841 The <literal>StartSel</literal>, <literal>StopSel</literal>
3842 and <literal>FragmentDelimiter</literal> strings must not exceed
3843 32Kb in length, but this was not checked for. An over-length value
3844 would typically crash the server.
3845 </para>
3846
3847 <para>
3848 The <productname>PostgreSQL</productname> Project thanks
3849 Xint Code for reporting this problem.
3850 (CVE-2026-6473)
3851 </para>
3852 </listitem>
3853
3854 <listitem>
3855 <!--
3856 Author: Michael Paquier <[email protected]>
3857 Branch: master [6d6348f03] 2026-05-11 05:13:46 -0700
3858 Branch: REL_18_STABLE [661095c40] 2026-05-11 05:13:47 -0700
3859 -->
3860 <para>
3861 Detect faulty input when restoring attribute MCV statistics
3862 (Michael Paquier)
3863 <ulink url="&commit_baseurl;661095c40">&sect;</ulink>
3864 </para>
3865
3866 <para>
3867 The statistics restore functions were insufficiently careful about
3868 validating most-common-value statistics, and would accept values
3869 that could crash the planner later on.
3870 </para>
3871
3872 <para>
3873 The <productname>PostgreSQL</productname> Project thanks
3874 Jeroen Gui for reporting this problem.
3875 (CVE-2026-6575)
3876 </para>
3877 </listitem>
3878
3879 <listitem>
3880 <!--
3881 Author: Tom Lane <[email protected]>
3882 Branch: master [76ab76f87] 2026-05-11 05:13:46 -0700
3883 Branch: REL_18_STABLE [ba27389c2] 2026-05-11 05:13:47 -0700
3884 Branch: REL_17_STABLE [4197c880c] 2026-05-11 05:13:49 -0700
3885 Branch: REL_16_STABLE [24e0e3254] 2026-05-11 05:13:50 -0700
3886 Branch: REL_15_STABLE [126a236ba] 2026-05-11 05:13:50 -0700
3887 Branch: REL_14_STABLE [a50ae8306] 2026-05-11 05:13:51 -0700
3888 Author: Tom Lane <[email protected]>
3889 Branch: master [ec8ded4b3] 2026-05-11 05:13:46 -0700
3890 Branch: REL_18_STABLE [c6e7a9ef3] 2026-05-11 05:13:47 -0700
3891 Branch: REL_17_STABLE [a386d14fe] 2026-05-11 05:13:49 -0700
3892 Branch: REL_16_STABLE [79b7847c7] 2026-05-11 05:13:50 -0700
3893 Branch: REL_15_STABLE [c3fff3950] 2026-05-11 05:13:50 -0700
3894 Branch: REL_14_STABLE [2c8226f52] 2026-05-11 05:13:51 -0700
3895 -->
3896 <para>
3897 Guard against malicious time zone names
3898 in <function>timeofday()</function>
3899 and <function>pg_strftime()</function> (Tom Lane)
3900 <ulink url="&commit_baseurl;ba27389c2">&sect;</ulink>
3901 <ulink url="&commit_baseurl;c6e7a9ef3">&sect;</ulink>
3902 </para>
3903
3904 <para>
3905 A crafted time zone setting could pass <literal>%</literal>
3906 sequences to <function>snprintf()</function>, potentially causing
3907 crashes or disclosure of server memory. Another path to similar
3908 results was to overflow the limited-size output buffer used
3909 by <function>pg_strftime()</function>.
3910 </para>
3911
3912 <para>
3913 The <productname>PostgreSQL</productname> Project thanks
3914 Xint Code for reporting this problem.
3915 (CVE-2026-6474)
3916 </para>
3917 </listitem>
3918
3919 <listitem>
3920 <!--
3921 Author: Nathan Bossart <[email protected]>
3922 Branch: master [4793fc41f] 2026-05-11 05:13:47 -0700
3923 Branch: REL_18_STABLE [a44780f41] 2026-05-11 05:13:47 -0700
3924 Branch: REL_17_STABLE [c27ba08cd] 2026-05-11 05:13:49 -0700
3925 Branch: REL_16_STABLE [d92852d62] 2026-05-11 05:13:50 -0700
3926 Branch: REL_15_STABLE [08c397b02] 2026-05-11 05:13:50 -0700
3927 Branch: REL_14_STABLE [8bca85e9f] 2026-05-11 05:13:51 -0700
3928 -->
3929 <para>
3930 When creating a multirange type, ensure the user
3931 has <literal>CREATE</literal> privilege on the schema specified for
3932 the multirange type (Jelte Fennema-Nio)
3933 <ulink url="&commit_baseurl;a44780f41">&sect;</ulink>
3934 </para>
3935
3936 <para>
3937 The multirange type can be put into a different schema than its
3938 parent range type, but we neglected to apply the required privilege
3939 check when doing so.
3940 </para>
3941
3942 <para>
3943 The <productname>PostgreSQL</productname> Project thanks
3944 Jelte Fennema-Nio for reporting this problem.
3945 (CVE-2026-6472)
3946 </para>
3947 </listitem>
3948
3949 <listitem>
3950 <!--
3951 Author: Michael Paquier <[email protected]>
3952 Branch: master [5924e256c] 2026-05-11 05:13:46 -0700
3953 Branch: REL_18_STABLE [d93ef4131] 2026-05-11 05:13:47 -0700
3954 Branch: REL_17_STABLE [c4e7435b3] 2026-05-11 05:13:48 -0700
3955 Branch: REL_16_STABLE [00e27235e] 2026-05-11 05:13:49 -0700
3956 Branch: REL_15_STABLE [c95275f18] 2026-05-11 05:13:50 -0700
3957 Branch: REL_14_STABLE [4608619a1] 2026-05-11 05:13:51 -0700
3958 Author: Heikki Linnakangas <[email protected]>
3959 Branch: REL_17_STABLE [8e34acfda] 2026-05-11 05:13:48 -0700
3960 Branch: REL_16_STABLE [1604939b2] 2026-05-11 05:13:49 -0700
3961 Branch: REL_15_STABLE [9dcfcb92f] 2026-05-11 05:13:50 -0700
3962 Branch: REL_14_STABLE [b282280e9] 2026-05-11 05:13:51 -0700
3963 -->
3964 <para>
3965 Use timing-safe string comparisons in authentication code
3966 (Michael Paquier)
3967 <ulink url="&commit_baseurl;d93ef4131">&sect;</ulink>
3968 </para>
3969
3970 <para>
3971 Use <function>timingsafe_bcmp()</function> instead
3972 of <function>memcmp()</function> or <function>strcmp()</function>
3973 when checking passwords, hashes, etc. It is not known whether the
3974 data dependency of those functions is usefully exploitable in any of
3975 these places, but in the interests of safety, replace them.
3976 </para>
3977
3978 <para>
3979 The <productname>PostgreSQL</productname> Project thanks
3980 Joe Conway for reporting this problem.
3981 (CVE-2026-6478)
3982 </para>
3983 </listitem>
3984
3985 <listitem>
3986 <!--
3987 Author: Nathan Bossart <[email protected]>
3988 Branch: master [bd4811493] 2026-05-11 05:13:47 -0700
3989 Branch: REL_18_STABLE [be0136440] 2026-05-11 05:13:48 -0700
3990 Branch: REL_17_STABLE [d88c7be15] 2026-05-11 05:13:49 -0700
3991 Branch: REL_16_STABLE [614474996] 2026-05-11 05:13:50 -0700
3992 Branch: REL_15_STABLE [e3a1f83ea] 2026-05-11 05:13:51 -0700
3993 Branch: REL_14_STABLE [8ac723b2b] 2026-05-11 05:13:51 -0700
3994 -->
3995 <para>
3996 Mark <function>PQfn()</function> as unsafe, and avoid using it
3997 within <application>libpq</application> (Nathan Bossart)
3998 <ulink url="&commit_baseurl;be0136440">&sect;</ulink>
3999 </para>
4000
4001 <para>
4002 For a non-integral result type, <function>PQfn()</function> is not
4003 passed the size of the output buffer, so it cannot check that the
4004 data returned by the server will fit. A malicious server could
4005 therefore overwrite client memory. This is unfixable without an
4006 API change, so mark the function as deprecated. Internally
4007 to <application>libpq</application>, use a variant version that can
4008 apply the missing check.
4009 </para>
4010
4011 <para>
4012 The <productname>PostgreSQL</productname> Project thanks
4013 Yu Kunpeng and Martin Heistermann for reporting this problem.
4014 (CVE-2026-6477)
4015 </para>
4016 </listitem>
4017
4018 <listitem>
4019 <!--
4020 Author: Michael Paquier <[email protected]>
4021 Branch: master [a1063eece] 2026-05-11 05:13:47 -0700
4022 Branch: REL_18_STABLE [6a67c540a] 2026-05-11 05:13:48 -0700
4023 Branch: REL_17_STABLE [8f881e188] 2026-05-11 05:13:49 -0700
4024 Branch: REL_16_STABLE [6778af13e] 2026-05-11 05:13:50 -0700
4025 Branch: REL_15_STABLE [0c83fe8e4] 2026-05-11 05:13:50 -0700
4026 Branch: REL_14_STABLE [498829dca] 2026-05-11 05:13:51 -0700
4027 -->
4028 <para>
4029 Prevent path traversal in <application>pg_basebackup</application>
4030 and <application>pg_rewind</application> (Michael Paquier)
4031 <ulink url="&commit_baseurl;6a67c540a">&sect;</ulink>
4032 </para>
4033
4034 <para>
4035 These applications failed to validate output file paths read from
4036 their input, so that a malicious source could overwrite any file
4037 writable by these applications. Constrain where data can be written
4038 by rejecting paths that are absolute or contain parent-directory
4039 references.
4040 </para>
4041
4042 <para>
4043 The <productname>PostgreSQL</productname> Project thanks XlabAI Team
4044 of Tencent Xuanwu Lab and Valery Gubanov for reporting this problem.
4045 (CVE-2026-6475)
4046 </para>
4047 </listitem>
4048
4049 <listitem>
4050 <!--
4051 Author: Tom Lane <[email protected]>
4052 Branch: master [43451a7a2] 2026-05-11 05:13:46 -0700
4053 Branch: REL_18_STABLE [c5790ec4f] 2026-05-11 05:13:47 -0700
4054 Branch: REL_17_STABLE [c4d04cc48] 2026-05-11 05:13:48 -0700
4055 Branch: REL_16_STABLE [5c1069c35] 2026-05-11 05:13:49 -0700
4056 Branch: REL_15_STABLE [84a9f2641] 2026-05-11 05:13:50 -0700
4057 Branch: REL_14_STABLE [074702525] 2026-05-11 05:13:51 -0700
4058 Branch: master [906ea101d] 2026-05-11 12:12:03 -0400
4059 Branch: REL_18_STABLE [05e73b5c3] 2026-05-11 12:12:03 -0400
4060 Branch: REL_17_STABLE [2b429d887] 2026-05-11 12:12:03 -0400
4061 Branch: REL_16_STABLE [6f0bff33d] 2026-05-11 12:12:03 -0400
4062 Branch: REL_15_STABLE [fc1fd3d97] 2026-05-11 12:12:03 -0400
4063 Branch: REL_14_STABLE [479823a71] 2026-05-11 12:12:03 -0400
4064 -->
4065 <para>
4066 Guard against field overflow
4067 within <filename>contrib/intarray</filename>'s <type>query_int</type>
4068 type and <filename>contrib/ltree</filename>'s <type>ltxtquery</type>
4069 type (Tom Lane)
4070 <ulink url="&commit_baseurl;c5790ec4f">&sect;</ulink>
4071 <ulink url="&commit_baseurl;05e73b5c3">&sect;</ulink>
4072 </para>
4073
4074 <para>
4075 Parsing of these query structures did not check for overflow of
4076 16-bit fields, so that construction of an invalid query tree was
4077 possible. This can crash the server when executing the query.
4078 </para>
4079
4080 <para>
4081 The <productname>PostgreSQL</productname> Project thanks
4082 Xint Code for reporting this problem.
4083 (CVE-2026-6473)
4084 </para>
4085 </listitem>
4086
4087 <listitem>
4088 <!--
4089 Author: Michael Paquier <[email protected]>
4090 Branch: master [2f1b16e86] 2026-05-11 05:13:46 -0700
4091 Branch: REL_18_STABLE [7f019f341] 2026-05-11 05:13:47 -0700
4092 Branch: REL_17_STABLE [8c3426110] 2026-05-11 05:13:48 -0700
4093 Branch: REL_16_STABLE [6b6b26fde] 2026-05-11 05:13:49 -0700
4094 Branch: REL_15_STABLE [9c2fa5b6a] 2026-05-11 05:13:50 -0700
4095 Branch: REL_14_STABLE [b545c3787] 2026-05-11 05:13:51 -0700
4096 -->
4097 <para>
4098 Guard against overly long values
4099 of <filename>contrib/ltree</filename>'s <type>lquery</type> type
4100 (Michael Paquier)
4101 <ulink url="&commit_baseurl;7f019f341">&sect;</ulink>
4102 </para>
4103
4104 <para>
4105 Values with more than 64K items caused internal overflows,
4106 potentially resulting in stack smashes or wrong answers.
4107 </para>
4108
4109 <para>
4110 The <productname>PostgreSQL</productname> Project thanks
4111 Vergissmeinnicht, A1ex, and Jihe Wang
4112 for reporting this problem.
4113 (CVE-2026-6473)
4114 </para>
4115 </listitem>
4116
4117 <listitem>
4118 <!--
4119 Author: Nathan Bossart <[email protected]>
4120 Branch: master [260e97733] 2026-05-11 05:13:47 -0700
4121 Branch: REL_18_STABLE [1ebda7da9] 2026-05-11 05:13:48 -0700
4122 Branch: REL_17_STABLE [2dc64ef28] 2026-05-11 05:13:49 -0700
4123 Branch: REL_16_STABLE [710995782] 2026-05-11 05:13:50 -0700
4124 Branch: REL_15_STABLE [8053235ab] 2026-05-11 05:13:51 -0700
4125 Branch: REL_14_STABLE [2b026df29] 2026-05-11 05:13:52 -0700
4126 -->
4127 <para>
4128 Prevent SQL injection and buffer overruns
4129 in <filename>contrib/spi</filename> (Nathan Bossart)
4130 <ulink url="&commit_baseurl;1ebda7da9">&sect;</ulink>
4131 </para>
4132
4133 <para>
4134 <function>check_foreign_key()</function> was insufficiently careful
4135 about quoting key values, and also used fixed-length buffers for
4136 constructing queries. While this module is only meant as example
4137 code, it still shouldn't contain such dangerous errors.
4138 </para>
4139
4140 <para>
4141 The <productname>PostgreSQL</productname> Project thanks
4142 Nikolay Samokhvalov for reporting this problem.
4143 (CVE-2026-6637)
4144 </para>
4145 </listitem>
4146
4147 <listitem>
4148 <!--
4149 Author: Richard Guo <[email protected]>
4150 Branch: master [f76686ce7] 2026-05-01 11:13:50 +0900
4151 Branch: REL_18_STABLE [e8fd5e579] 2026-05-01 11:16:36 +0900
4152 Branch: master [ba82de48e] 2026-05-08 10:57:50 +0900
4153 Branch: REL_18_STABLE [1132af22c] 2026-05-08 10:59:13 +0900
4154 Branch: master [a1b754558] 2026-05-08 12:45:51 +0900
4155 Branch: REL_18_STABLE [5c214b58b] 2026-05-08 12:47:26 +0900
4156 Branch: master [5a55ea507] 2026-05-05 10:22:53 +0900
4157 Branch: REL_18_STABLE [b62f514ac] 2026-05-05 10:26:17 +0900
4158 Branch: REL_17_STABLE [d0e73bb18] 2026-05-05 10:28:24 +0900
4159 Branch: REL_16_STABLE [748fe9e60] 2026-05-05 10:30:37 +0900
4160 Branch: REL_15_STABLE [872c9fae7] 2026-05-05 10:32:25 +0900
4161 Branch: REL_14_STABLE [8395446df] 2026-05-05 10:33:47 +0900
4162 Branch: master [574581b50] 2026-05-05 10:23:31 +0900
4163 Branch: REL_18_STABLE [bed3ffbf9] 2026-05-05 10:27:06 +0900
4164 Branch: REL_17_STABLE [13226050e] 2026-05-05 10:29:01 +0900
4165 Branch: REL_16_STABLE [5a24cef08] 2026-05-05 10:31:17 +0900
4166 Branch: REL_15_STABLE [bab4f7fa5] 2026-05-05 10:32:42 +0900
4167 Branch: REL_14_STABLE [172034f6e] 2026-05-05 10:34:07 +0900
4168 -->
4169 <para>
4170 Check for nondeterministic collations before assuming that an
4171 equality condition on a collatable type implies uniqueness
4172 (Richard Guo)
4173 <ulink url="&commit_baseurl;e8fd5e579">&sect;</ulink>
4174 <ulink url="&commit_baseurl;1132af22c">&sect;</ulink>
4175 <ulink url="&commit_baseurl;5c214b58b">&sect;</ulink>
4176 <ulink url="&commit_baseurl;b62f514ac">&sect;</ulink>
4177 <ulink url="&commit_baseurl;bed3ffbf9">&sect;</ulink>
4178 </para>
4179
4180 <para>
4181 Numerous planner optimizations assume that, for example, at most one
4182 table row can satisfy <literal>WHERE x = 'abc'</literal> if there is
4183 a unique index on <literal>x</literal>. However this conclusion is
4184 unsafe in general if the index and the <literal>WHERE</literal>
4185 clause have different collations attached. It is safe when both
4186 collations are deterministic, because that property essentially
4187 requires that equality of two strings means bitwise equality. But
4188 nondeterministic collations don't act that way, so that optimizing
4189 on the assumption of unique matches can give wrong query answers if
4190 either the <literal>WHERE</literal> clause or the index has a
4191 nondeterministic collation.
4192 </para>
4193 </listitem>
4194
4195 <listitem>
4196 <!--
4197 Author: Tom Lane <[email protected]>
4198 Branch: master [cfcd57111] 2026-04-20 14:48:23 -0400
4199 Branch: REL_18_STABLE [16fb94605] 2026-04-20 14:48:23 -0400
4200 Branch: REL_17_STABLE [766d40286] 2026-04-20 14:48:23 -0400
4201 Branch: REL_16_STABLE [d509be4ac] 2026-04-20 14:48:23 -0400
4202 Branch: master [f0ac6d494] 2026-04-20 19:24:52 -0400
4203 Branch: REL_17_STABLE [53cb4ec1d] 2026-04-20 19:24:46 -0400
4204 Branch: REL_16_STABLE [798dabe83] 2026-04-20 19:24:46 -0400
4205 -->
4206 <para>
4207 Fix incomplete removal of relation references
4208 in <literal>RestrictInfo</literal> structs during join removal
4209 (Tom Lane)
4210 <ulink url="&commit_baseurl;16fb94605">&sect;</ulink>
4211 </para>
4212
4213 <para>
4214 This oversight has been shown to result in planner failures such as
4215 unexpected <quote>FULL JOIN is only supported with merge-joinable or
4216 hash-joinable join conditions</quote> errors. It may also have
4217 caused failure to consider valid plans in other cases.
4218 </para>
4219 </listitem>
4220
4221 <listitem>
4222 <!--
4223 Author: Richard Guo <[email protected]>
4224 Branch: master [c1408956e] 2026-04-09 16:41:31 +0900
4225 Branch: REL_18_STABLE [8e8b2bef7] 2026-04-09 16:43:28 +0900
4226 -->
4227 <para>
4228 Improve planner's matching of partition key columns to sub-query
4229 outputs (Richard Guo)
4230 <ulink url="&commit_baseurl;8e8b2bef7">&sect;</ulink>
4231 </para>
4232
4233 <para>
4234 Strip no-op PlaceHolderVars from operands before comparing them to
4235 partition keys. This change enables partition pruning to succeed in
4236 some cases where it previously failed to recognize that a partition
4237 need not be scanned.
4238 </para>
4239 </listitem>
4240
4241 <listitem>
4242 <!--
4243 Author: Alexander Korotkov <[email protected]>
4244 Branch: master [07b7a964d] 2026-03-20 15:46:30 +0200
4245 Branch: REL_18_STABLE [e8b9d6497] 2026-03-20 15:47:11 +0200
4246 -->
4247 <para>
4248 Fix self-join removal to handle join clauses that are bare boolean
4249 columns, e.g. <literal>ON t1.boolcol</literal> (Andrei Lepikhov,
4250 Tender Wang, Alexander Korotkov)
4251 <ulink url="&commit_baseurl;e8b9d6497">&sect;</ulink>
4252 </para>
4253
4254 <para>
4255 Previously such a case led to a <quote>no relation entry
4256 for relid <replaceable>N</replaceable></quote> error.
4257 </para>
4258 </listitem>
4259
4260 <listitem>
4261 <!--
4262 Author: Dean Rasheed <[email protected]>
4263 Branch: master [5548a969b] 2026-04-22 11:50:17 +0100
4264 Branch: REL_18_STABLE [f3d03fbd5] 2026-04-22 11:50:18 +0100
4265 -->
4266 <para>
4267 Fix <literal>UPDATE/DELETE ... WHERE CURRENT OF</literal> to work on
4268 tables with virtual generated columns (Satyanarayana Narlapuram,
4269 Dean Rasheed)
4270 <ulink url="&commit_baseurl;f3d03fbd5">&sect;</ulink>
4271 </para>
4272 </listitem>
4273
4274 <listitem>
4275 <!--
4276 Author: Dean Rasheed <[email protected]>
4277 Branch: master [783425175] 2026-04-22 09:03:44 +0100
4278 Branch: REL_18_STABLE [cf38dedf6] 2026-04-22 09:03:44 +0100
4279 -->
4280 <para>
4281 Fix expansion of virtual generated columns
4282 in <literal>EXCLUDED</literal> column references in <literal>INSERT
4283 ... ON CONFLICT</literal> (Satyanarayana Narlapuram, Dean Rasheed)
4284 <ulink url="&commit_baseurl;cf38dedf6">&sect;</ulink>
4285 </para>
4286 </listitem>
4287
4288 <listitem>
4289 <!--
4290 Author: Richard Guo <[email protected]>
4291 Branch: master [c6a79be3f] 2026-04-21 14:28:26 +0900
4292 Branch: REL_18_STABLE [e528bfe97] 2026-04-21 14:29:33 +0900
4293 Branch: REL_17_STABLE [9d6208939] 2026-04-21 14:31:15 +0900
4294 Branch: REL_16_STABLE [07b257189] 2026-04-21 14:33:07 +0900
4295 Branch: REL_15_STABLE [7062bd577] 2026-04-21 14:33:57 +0900
4296 Branch: REL_14_STABLE [8e39951be] 2026-04-21 14:35:43 +0900
4297 -->
4298 <para>
4299 Fix incorrect handling of <literal>NEW</literal> generated columns
4300 in rule actions and rule qualifications (Richard Guo, Dean Rasheed)
4301 <ulink url="&commit_baseurl;e528bfe97">&sect;</ulink>
4302 </para>
4303
4304 <para>
4305 Previously, such column references would produce NULL
4306 in <literal>INSERT</literal> cases, or be equivalent to
4307 the <literal>OLD</literal> value in <literal>UPDATE</literal> cases.
4308 </para>
4309 </listitem>
4310
4311 <listitem>
4312 <!--
4313 Author: Robert Haas <[email protected]>
4314 Branch: master [570e2fcc0] 2026-03-24 06:28:33 -0400
4315 Branch: REL_18_STABLE [cceb9c18a] 2026-03-24 06:28:32 -0400
4316 -->
4317 <para>
4318 Fix spurious <quote>indexes on virtual generated columns are not
4319 supported</quote> errors (Robert Haas)
4320 <ulink url="&commit_baseurl;cceb9c18a">&sect;</ulink>
4321 </para>
4322
4323 <para>
4324 Creation of an expression index could sometimes incorrectly report
4325 this error.
4326 </para>
4327 </listitem>
4328
4329 <listitem>
4330 <!--
4331 Author: Tom Lane <[email protected]>
4332 Branch: REL_18_STABLE [11c2c0cc8] 2026-04-06 14:22:17 -0400
4333 Branch: REL_17_STABLE [681a91d29] 2026-04-06 14:22:17 -0400
4334 Branch: REL_16_STABLE [3c7a6bbe6] 2026-04-06 14:22:17 -0400
4335 Branch: REL_15_STABLE [07e833e3c] 2026-04-06 14:22:17 -0400
4336 Branch: REL_14_STABLE [40fa04e7c] 2026-04-06 14:22:17 -0400
4337 -->
4338 <para>
4339 Fix spurious <quote>generated columns are not supported in COPY FROM
4340 WHERE conditions</quote> errors (Tom Lane)
4341 <ulink url="&commit_baseurl;11c2c0cc8">&sect;</ulink>
4342 </para>
4343
4344 <para>
4345 Use of a system column in a <literal>COPY FROM WHERE</literal>
4346 condition could sometimes incorrectly report this error.
4347 </para>
4348 </listitem>
4349
4350 <listitem>
4351 <!--
4352 Author: Alexander Korotkov <[email protected]>
4353 Branch: master [177037341] 2026-03-05 19:49:28 +0200
4354 Branch: REL_18_STABLE [13fab378e] 2026-03-05 19:50:06 +0200
4355 Branch: REL_17_STABLE [2dcac93c0] 2026-03-05 19:56:42 +0200
4356 Branch: REL_16_STABLE [f6e63d4b8] 2026-03-05 20:02:08 +0200
4357 Branch: REL_15_STABLE [8bfaae6fb] 2026-03-05 19:57:32 +0200
4358 -->
4359 <para>
4360 Correctly report a serialization failure
4361 when <command>MERGE</command> encounters a concurrently-updated
4362 tuple in repeatable-read or serializable mode (Tender Wang)
4363 <ulink url="&commit_baseurl;13fab378e">&sect;</ulink>
4364 </para>
4365
4366 <para>
4367 Previously, such cases behaved the same as in lower isolation
4368 levels.
4369 </para>
4370 </listitem>
4371
4372 <listitem>
4373 <!--
4374 Author: Andrew Dunstan <[email protected]>
4375 Branch: master [6cf49e804] 2026-04-30 11:04:57 -0400
4376 Branch: REL_18_STABLE [149c875fc] 2026-04-30 11:05:29 -0400
4377 Branch: REL_17_STABLE [a0104b447] 2026-04-30 11:14:37 -0400
4378 Branch: REL_16_STABLE [7bb519635] 2026-04-30 11:14:26 -0400
4379 Branch: REL_15_STABLE [76d15a7ee] 2026-04-30 11:14:12 -0400
4380 Branch: REL_14_STABLE [81b56b47c] 2026-04-30 11:13:50 -0400
4381 -->
4382 <para>
4383 Fix <literal>CREATE TABLE ... LIKE ... INCLUDING
4384 STATISTICS</literal> for cases where the source table has dropped
4385 column(s) (Julien Tachoires)
4386 <ulink url="&commit_baseurl;149c875fc">&sect;</ulink>
4387 </para>
4388
4389 <para>
4390 In such cases, extended statistics objects could be copied
4391 incorrectly, or the command could give an incorrect error.
4392 </para>
4393 </listitem>
4394
4395 <listitem>
4396 <!--
4397 Author: Michael Paquier <[email protected]>
4398 Branch: master [9d3e094f1] 2026-04-22 10:32:10 +0900
4399 Branch: REL_18_STABLE [5713ac248] 2026-04-22 10:34:33 +0900
4400 Branch: REL_17_STABLE [becf6d269] 2026-04-22 10:34:35 +0900
4401 Branch: REL_16_STABLE [313355d68] 2026-04-22 10:34:37 +0900
4402 Branch: REL_15_STABLE [0859000d0] 2026-04-22 10:34:38 +0900
4403 Branch: REL_14_STABLE [d809b16d1] 2026-04-22 10:34:40 +0900
4404 -->
4405 <para>
4406 Allow <literal>ALTER INDEX ... ATTACH PARTITION</literal> to mark
4407 the parent index valid if appropriate (Sami Imseih)
4408 <ulink url="&commit_baseurl;5713ac248">&sect;</ulink>
4409 </para>
4410
4411 <para>
4412 There are edge cases in which a partitioned index might remain
4413 marked as invalid even when all its leaf indexes are valid. This
4414 change provides a mechanism whereby a user can correct such a
4415 situation without resorting to manual catalog updates.
4416 </para>
4417 </listitem>
4418
4419 <listitem>
4420 <!--
4421 Author: Álvaro Herrera <[email protected]>
4422 Branch: master [e7975f1c0] 2026-03-20 14:38:50 +0100
4423 Branch: REL_18_STABLE [6958077ce] 2026-03-20 14:38:50 +0100
4424 -->
4425 <para>
4426 Fix <literal>ALTER TABLE ... SET NOT NULL</literal> to invoke
4427 object-access hook functions only after completing the catalog
4428 change (Artur Zakirov)
4429 <ulink url="&commit_baseurl;6958077ce">&sect;</ulink>
4430 </para>
4431 </listitem>
4432
4433 <listitem>
4434 <!--
4435 Author: Jeff Davis <[email protected]>
4436 Branch: master [703fee3b2] 2026-03-19 15:07:43 -0700
4437 Branch: REL_18_STABLE [c11f87b1a] 2026-03-19 14:59:30 -0700
4438 Branch: REL_17_STABLE [876fa84a2] 2026-03-19 15:02:18 -0700
4439 Branch: REL_16_STABLE [a19edb66a] 2026-03-19 15:00:58 -0700
4440 Branch: REL_15_STABLE [3a35ab1d0] 2026-03-19 15:01:22 -0700
4441 Branch: REL_14_STABLE [c6f369e58] 2026-03-19 15:01:45 -0700
4442 -->
4443 <para>
4444 Fix <command>ALTER FOREIGN DATA WRAPPER</command> to not drop the
4445 wrapper object's dependency on its handler function (Jeff Davis)
4446 <ulink url="&commit_baseurl;c11f87b1a">&sect;</ulink>
4447 </para>
4448 </listitem>
4449
4450 <listitem>
4451 <!--
4452 Author: Fujii Masao <[email protected]>
4453 Branch: master [2497dac55] 2026-03-30 14:37:33 +0900
4454 Branch: REL_18_STABLE [5db5e3396] 2026-03-30 14:38:58 +0900
4455 -->
4456 <para>
4457 Fix loss of deferrability of foreign-key triggers (Yasuo Honda)
4458 <ulink url="&commit_baseurl;5db5e3396">&sect;</ulink>
4459 </para>
4460
4461 <para>
4462 Previously, a foreign key defined as <literal>DEFERRABLE INITIALLY
4463 DEFERRED</literal> would behave as <literal>NOT DEFERRABLE</literal>
4464 after being set to <literal>NOT ENFORCED</literal> status and then
4465 back to <literal>ENFORCED</literal>.
4466 </para>
4467
4468 <para>
4469 If you have a foreign key with this problem, it can be repaired
4470 (after installing this update) by again setting it to <literal>NOT
4471 ENFORCED</literal> and then back to <literal>ENFORCED</literal>.
4472 </para>
4473 </listitem>
4474
4475 <listitem>
4476 <!--
4477 Author: Tom Lane <[email protected]>
4478 Branch: master [4edd6036d] 2026-04-07 14:45:37 -0400
4479 Branch: REL_18_STABLE [49f3cb453] 2026-04-07 14:45:33 -0400
4480 -->
4481 <para>
4482 Fix <literal>WITHOUT OVERLAPS</literal> to allow domains (Jian He)
4483 <ulink url="&commit_baseurl;49f3cb453">&sect;</ulink>
4484 </para>
4485
4486 <para>
4487 <literal>UNIQUE/PRIMARY KEY ... WITHOUT OVERLAPS</literal> requires
4488 the no-overlap column to be a range or multirange, but it should
4489 allow a domain over such a type too.
4490 </para>
4491 </listitem>
4492
4493 <listitem>
4494 <!--
4495 Author: Heikki Linnakangas <[email protected]>
4496 Branch: master [dd4069197] 2026-04-23 21:28:11 +0300
4497 Branch: REL_18_STABLE [ff8f27d6e] 2026-04-23 21:28:59 +0300
4498 Branch: REL_17_STABLE [54343f6f9] 2026-04-23 21:31:32 +0300
4499 Branch: REL_16_STABLE [06e304524] 2026-04-23 21:33:02 +0300
4500 Branch: REL_15_STABLE [34ebeb15c] 2026-04-23 21:33:25 +0300
4501 Branch: REL_14_STABLE [c7a1d5fc6] 2026-04-23 21:33:39 +0300
4502 -->
4503 <para>
4504 Disallow making a composite type be a member of itself via a
4505 multirange (Heikki Linnakangas)
4506 <ulink url="&commit_baseurl;ff8f27d6e">&sect;</ulink>
4507 </para>
4508
4509 <para>
4510 We already forbade such cases when the intermediate type is a
4511 domain, array, composite type, or range; but multiranges were
4512 overlooked.
4513 </para>
4514 </listitem>
4515
4516 <listitem>
4517 <!--
4518 Author: David Rowley <[email protected]>
4519 Branch: master [0d866282b] 2026-03-30 16:14:34 +1300
4520 Branch: REL_18_STABLE [49315de0c] 2026-03-30 16:16:09 +1300
4521 Branch: REL_17_STABLE [d29808e35] 2026-03-30 16:16:39 +1300
4522 Branch: REL_16_STABLE [1bd90c887] 2026-03-30 16:17:14 +1300
4523 Branch: REL_15_STABLE [6b2e091f0] 2026-03-30 16:17:39 +1300
4524 Branch: REL_14_STABLE [6ce5c310b] 2026-03-30 16:18:13 +1300
4525 -->
4526 <para>
4527 Fix datum-image comparisons to be insensitive to sign-extension
4528 variations (David Rowley)
4529 <ulink url="&commit_baseurl;49315de0c">&sect;</ulink>
4530 </para>
4531
4532 <para>
4533 This fixes some situations that previously led to <quote>could not
4534 find memoization table entry</quote> errors or wrong query results.
4535 </para>
4536 </listitem>
4537
4538 <listitem>
4539 <!--
4540 Author: David Rowley <[email protected]>
4541 Branch: master [94219a73f] 2026-04-24 14:03:12 +1200
4542 Branch: REL_18_STABLE [035c520db] 2026-04-24 14:03:41 +1200
4543 Branch: REL_17_STABLE [3fda3e12f] 2026-04-24 14:04:05 +1200
4544 Branch: REL_16_STABLE [a2a0060d5] 2026-04-24 14:04:31 +1200
4545 Branch: REL_15_STABLE [622f8b530] 2026-04-24 14:04:55 +1200
4546 Branch: REL_14_STABLE [109de35b7] 2026-04-24 14:05:23 +1200
4547 -->
4548 <para>
4549 Fix incorrect logic for hashed <literal>IN</literal>/<literal>NOT
4550 IN</literal> with non-strict equality operator (Chengpeng Yan)
4551 <ulink url="&commit_baseurl;035c520db">&sect;</ulink>
4552 </para>
4553
4554 <para>
4555 The previous coding could crash or give wrong answers. All built-in
4556 data types have strict equality operators, so that this issue could
4557 only arise with an extension data type.
4558 </para>
4559 </listitem>
4560
4561 <listitem>
4562 <!--
4563 Author: Tom Lane <[email protected]>
4564 Branch: master [a50777680] 2026-04-22 12:41:00 -0400
4565 Branch: REL_18_STABLE [580e7be88] 2026-04-22 12:41:00 -0400
4566 Branch: REL_17_STABLE [c97a28618] 2026-04-22 12:41:00 -0400
4567 Branch: REL_16_STABLE [e1e60f148] 2026-04-22 12:41:01 -0400
4568 Branch: REL_15_STABLE [f60d25986] 2026-04-22 12:41:01 -0400
4569 Branch: REL_14_STABLE [8a6f08c0c] 2026-04-22 12:41:01 -0400
4570 -->
4571 <para>
4572 Truncate overly-long locale-specific numeric symbols
4573 in <function>to_char()</function> (Tom Lane)
4574 <ulink url="&commit_baseurl;580e7be88">&sect;</ulink>
4575 </para>
4576
4577 <para>
4578 If a locale specified a currency symbol, thousands separator, or
4579 decimal or sign symbol more than 8 bytes long, a buffer overrun was
4580 possible. No such locales exist in the real world, and it's
4581 impractical for an unprivileged attacker to install a malicious
4582 locale definition underneath a Postgres server; but for safety's
4583 sake check for overlength symbols and truncate if needed.
4584 </para>
4585 </listitem>
4586
4587 <listitem>
4588 <!--
4589 Author: Tom Lane <[email protected]>
4590 Branch: master [d7970e7e9] 2026-04-22 12:02:15 -0400
4591 Branch: REL_18_STABLE [00c6e0819] 2026-04-22 12:02:15 -0400
4592 Branch: REL_17_STABLE [ea5f0d176] 2026-04-22 12:02:15 -0400
4593 Branch: REL_16_STABLE [42383d32d] 2026-04-22 12:02:15 -0400
4594 Branch: REL_15_STABLE [0b196d3db] 2026-04-22 12:02:15 -0400
4595 Branch: REL_14_STABLE [21a24d709] 2026-04-22 12:02:15 -0400
4596 Branch: master [844bb90d4] 2026-04-22 10:47:56 -0400
4597 Branch: REL_18_STABLE [c2bfeb3bb] 2026-04-22 11:04:35 -0400
4598 Branch: REL_17_STABLE [a5426dbf8] 2026-04-22 11:05:51 -0400
4599 Branch: REL_16_STABLE [17f72e037] 2026-04-22 11:06:47 -0400
4600 Branch: REL_15_STABLE [f852c9093] 2026-04-22 11:09:02 -0400
4601 Branch: REL_14_STABLE [6cae0c2bd] 2026-04-22 11:09:21 -0400
4602 -->
4603 <para>
4604 Prevent buffer overruns when parsing an affix file for
4605 an <literal>Ispell</literal> dictionary (Tom Lane)
4606 <ulink url="&commit_baseurl;00c6e0819">&sect;</ulink>
4607 <ulink url="&commit_baseurl;c2bfeb3bb">&sect;</ulink>
4608 </para>
4609
4610 <para>
4611 A corrupt or malicious affix file could crash the server.
4612 This is not considered a security issue because text search
4613 configuration files are presumed trustworthy, but it still seems
4614 worth fixing.
4615 </para>
4616 </listitem>
4617
4618 <listitem>
4619 <!--
4620 Author: Richard Guo <[email protected]>
4621 Branch: master [8b6c89e37] 2026-04-09 19:28:33 +0900
4622 Branch: REL_18_STABLE [bfc7dff26] 2026-04-09 19:30:37 +0900
4623 Branch: REL_17_STABLE [f8736f8bc] 2026-04-09 19:32:09 +0900
4624 Branch: REL_16_STABLE [0fe032e6a] 2026-04-09 19:34:02 +0900
4625 Branch: REL_15_STABLE [4da71fc37] 2026-04-09 19:35:08 +0900
4626 Branch: REL_14_STABLE [305cf0df0] 2026-04-09 19:36:13 +0900
4627 -->
4628 <para>
4629 Guard against integer overflow in calculations of frame start and
4630 end positions for window aggregates (Richard Guo)
4631 <ulink url="&commit_baseurl;bfc7dff26">&sect;</ulink>
4632 </para>
4633
4634 <para>
4635 Very large user-specified offsets (close to INT64_MAX) could result
4636 in errors or incorrect query results.
4637 </para>
4638 </listitem>
4639
4640 <listitem>
4641 <!--
4642 Author: Tom Lane <[email protected]>
4643 Branch: master [6582010c8] 2026-04-06 13:14:53 -0400
4644 Branch: REL_18_STABLE [14bf2c39e] 2026-04-06 13:14:50 -0400
4645 Branch: REL_17_STABLE [d6c9432cb] 2026-04-06 13:14:50 -0400
4646 Branch: REL_16_STABLE [bb959269e] 2026-04-06 13:14:50 -0400
4647 -->
4648 <para>
4649 Fix <function>array_agg_array_combine()</function> to combine the
4650 arrays' null bitmaps correctly (Dmytro Astapov)
4651 <ulink url="&commit_baseurl;14bf2c39e">&sect;</ulink>
4652 </para>
4653
4654 <para>
4655 This mistake resulted in sometimes-incorrect output from
4656 parallelized <function>array_agg(anyarray)</function> calculations.
4657 </para>
4658 </listitem>
4659
4660 <listitem>
4661 <!--
4662 Author: Michael Paquier <[email protected]>
4663 Branch: master [5941e7f09] 2026-04-30 18:44:38 +0900
4664 Branch: REL_18_STABLE [6cb307251] 2026-04-30 18:44:41 +0900
4665 Branch: REL_17_STABLE [5499be332] 2026-04-30 18:44:43 +0900
4666 Branch: REL_16_STABLE [3b35c10a4] 2026-04-30 18:44:45 +0900
4667 -->
4668 <para>
4669 Retry <function>sync_file_range()</function> if it returns error
4670 code <literal>EINTR</literal> (DaeMyung Kang)
4671 <ulink url="&commit_baseurl;6cb307251">&sect;</ulink>
4672 </para>
4673 </listitem>
4674
4675 <listitem>
4676 <!--
4677 Author: Michael Paquier <[email protected]>
4678 Branch: master [80156cee0] 2026-04-11 17:02:52 +0900
4679 Branch: REL_18_STABLE [b081c5b07] 2026-04-11 17:03:04 +0900
4680 Branch: REL_17_STABLE [a4fefb3e0] 2026-04-11 17:03:06 +0900
4681 Branch: REL_16_STABLE [c7cdcbd3e] 2026-04-11 17:03:08 +0900
4682 Branch: REL_15_STABLE [c6d3f0585] 2026-04-11 17:03:10 +0900
4683 -->
4684 <para>
4685 Fix incorrect behavior
4686 of <function>pg_stat_reset_single_table_counters()</function> on a
4687 shared catalog (Chao Li)
4688 <ulink url="&commit_baseurl;b081c5b07">&sect;</ulink>
4689 </para>
4690
4691 <para>
4692 Such cases had a side-effect of resetting the
4693 current database's <literal>stat_reset_timestamp</literal>, which
4694 was unintended.
4695 </para>
4696 </listitem>
4697
4698 <listitem>
4699 <!--
4700 Author: Amit Kapila <[email protected]>
4701 Branch: master [090c4297e] 2026-04-20 10:31:11 +0530
4702 Branch: REL_18_STABLE [44c8dc280] 2026-04-20 10:23:22 +0530
4703 Branch: REL_17_STABLE [88d7fdcc9] 2026-04-20 10:17:47 +0530
4704 Branch: REL_16_STABLE [d052f6c7d] 2026-04-20 10:13:55 +0530
4705 -->
4706 <para>
4707 Update activity statistics when a parallel apply worker is idle
4708 (Zhijie Hou)
4709 <ulink url="&commit_baseurl;44c8dc280">&sect;</ulink>
4710 </para>
4711
4712 <para>
4713 Previously, statistics from a recently-completed transaction might
4714 go unreported for long intervals, particularly if the workload is
4715 light.
4716 </para>
4717 </listitem>
4718
4719 <listitem>
4720 <!--
4721 Author: Richard Guo <[email protected]>
4722 Branch: master [77d0e82e5] 2026-04-11 16:38:47 +0900
4723 Branch: REL_18_STABLE [13e20d1c9] 2026-04-11 16:40:34 +0900
4724 Branch: REL_17_STABLE [93ed18720] 2026-04-11 16:41:58 +0900
4725 -->
4726 <para>
4727 Fix <quote>no relation entry for relid 0</quote> failure while
4728 estimating array lengths in set operations (Tender Wang)
4729 <ulink url="&commit_baseurl;13e20d1c9">&sect;</ulink>
4730 </para>
4731 </listitem>
4732
4733 <listitem>
4734 <!--
4735 Author: Andrew Dunstan <[email protected]>
4736 Branch: master [2b5ba2a0a] 2026-04-10 07:13:08 -0400
4737 Branch: REL_18_STABLE [c3e436b1c] 2026-04-10 10:28:00 -0400
4738 Branch: REL_17_STABLE [c05c3baf1] 2026-04-10 10:27:43 -0400
4739 Branch: REL_16_STABLE [e630f65d0] 2026-04-10 10:27:16 -0400
4740 Branch: REL_15_STABLE [c88ad3a21] 2026-04-10 10:26:50 -0400
4741 Branch: REL_14_STABLE [de32a01e7] 2026-04-10 10:22:48 -0400
4742 -->
4743 <para>
4744 Fix buffer overread when <function>pglz_decompress()</function>
4745 receives corrupt input (Andrew Dunstan)
4746 <ulink url="&commit_baseurl;c3e436b1c">&sect;</ulink>
4747 </para>
4748
4749 <para>
4750 It was possible to read a few bytes past the end of the input, which
4751 in very unlucky cases might cause a crash.
4752 </para>
4753 </listitem>
4754
4755 <listitem>
4756 <!--
4757 Author: Andrew Dunstan <[email protected]>
4758 Branch: master [2478bd5db] 2026-04-10 07:13:08 -0400
4759 Branch: REL_18_STABLE [3e4955630] 2026-04-10 10:21:38 -0400
4760 Branch: REL_17_STABLE [2e373785e] 2026-04-10 10:21:39 -0400
4761 -->
4762 <para>
4763 Fix incremental JSON parser's handling of numeric tokens that cross
4764 input buffer boundaries (Andrew Dunstan)
4765 <ulink url="&commit_baseurl;3e4955630">&sect;</ulink>
4766 </para>
4767
4768 <para>
4769 It was possible to accept an incorrectly-formatted number, leading
4770 to failures later.
4771 </para>
4772 </listitem>
4773
4774 <listitem>
4775 <!--
4776 Author: Robert Haas <[email protected]>
4777 Branch: master [ffc226ab6] 2026-03-09 06:45:32 -0400
4778 Branch: REL_18_STABLE [9540c0e5d] 2026-03-09 06:46:20 -0400
4779 Branch: REL_17_STABLE [076bc57fa] 2026-03-09 06:55:10 -0400
4780 -->
4781 <para>
4782 Prevent bloating relation visibility maps during restore of an
4783 incremental backup (Robert Haas)
4784 <ulink url="&commit_baseurl;9540c0e5d">&sect;</ulink>
4785 </para>
4786
4787 <para>
4788 Restore could append many blocks of zeroes to a visibility map, due
4789 to incorrect computation of the expected file length. This does not
4790 result in data corruption, but it could waste a substantial amount
4791 of disk space.
4792 </para>
4793 </listitem>
4794
4795 <listitem>
4796 <!--
4797 Author: Jeff Davis <[email protected]>
4798 Branch: master [dbf217c1c] 2026-04-22 10:22:44 -0700
4799 Branch: REL_18_STABLE [03c4f243e] 2026-04-22 10:23:44 -0700
4800 Branch: REL_17_STABLE [9dda30dd3] 2026-04-22 10:23:54 -0700
4801 -->
4802 <para>
4803 Use C collation, not the database's default collation, in catalog
4804 cache lookups on text columns (Jeff Davis)
4805 <ulink url="&commit_baseurl;03c4f243e">&sect;</ulink>
4806 </para>
4807
4808 <para>
4809 This avoids failures in edge cases such as physical replication
4810 startup, where there is no identified database so that a default
4811 collation cannot be determined.
4812 </para>
4813 </listitem>
4814
4815 <listitem>
4816 <!--
4817 Author: Fujii Masao <[email protected]>
4818 Branch: master [db93032a7] 2026-04-08 11:22:21 +0900
4819 Branch: REL_18_STABLE [58c1188a3] 2026-04-08 11:23:13 +0900
4820 Branch: REL_17_STABLE [15910b1c3] 2026-04-08 11:24:00 +0900
4821 Branch: REL_18_STABLE [acf49bfed] 2026-04-09 15:25:40 +0900
4822 Branch: REL_17_STABLE [586f4266f] 2026-04-09 15:30:59 +0900
4823 Author: Amit Kapila <[email protected]>
4824 Branch: master [1362bc33e] 2025-12-11 03:49:28 +0000
4825 Branch: REL_18_STABLE [94efd308b] 2026-04-08 11:19:31 +0900
4826 Branch: REL_17_STABLE [4bed04d39] 2026-04-08 11:21:14 +0900
4827 -->
4828 <para>
4829 Prevent stuck slotsync worker processes from blocking promotion of a
4830 standby server (Nisha Moond, Ajin Cherian)
4831 <ulink url="&commit_baseurl;58c1188a3">&sect;</ulink>
4832 <ulink url="&commit_baseurl;acf49bfed">&sect;</ulink>
4833 <ulink url="&commit_baseurl;94efd308b">&sect;</ulink>
4834 </para>
4835
4836 <para>
4837 A worker process that was vainly waiting for a response from the
4838 primary would delay promotion for an unreasonable amount of time.
4839 </para>
4840 </listitem>
4841
4842 <listitem>
4843 <!--
4844 Author: Amit Kapila <[email protected]>
4845 Branch: master [85c17f612] 2026-04-13 10:06:50 +0530
4846 Branch: REL_18_STABLE [540fe8fb5] 2026-04-13 09:42:51 +0530
4847 Branch: REL_17_STABLE [91741b7cb] 2026-04-13 09:21:34 +0530
4848 -->
4849 <para>
4850 Fix excessive log output from idle slotsync worker processes
4851 (Zhijie Hou)
4852 <ulink url="&commit_baseurl;540fe8fb5">&sect;</ulink>
4853 </para>
4854 </listitem>
4855
4856 <listitem>
4857 <!--
4858 Author: Tom Lane <[email protected]>
4859 Branch: master [739477345] 2026-03-30 13:59:58 -0400
4860 Branch: REL_18_STABLE [adb7873bb] 2026-03-30 13:59:54 -0400
4861 Branch: REL_17_STABLE [1f5b6a5e5] 2026-03-30 13:59:54 -0400
4862 Branch: REL_16_STABLE [59c139d53] 2026-03-30 13:59:54 -0400
4863 Branch: REL_15_STABLE [811f3263a] 2026-03-30 13:59:54 -0400
4864 Branch: REL_14_STABLE [7cd23aad2] 2026-03-30 13:59:54 -0400
4865 -->
4866 <para>
4867 Ensure that tuplestore data structures are internally consistent
4868 even after an error (Tom Lane)
4869 <ulink url="&commit_baseurl;adb7873bb">&sect;</ulink>
4870 </para>
4871
4872 <para>
4873 The code was previously careless about this, which is fine most of
4874 the time but is problematic for the tuplestore backing
4875 a <literal>WITH HOLD</literal> cursor. In v15 and before this
4876 leads to easily-reproducible crashes; later branches are not known
4877 to be vulnerable, but it seems best to preserve consistency in all.
4878 </para>
4879 </listitem>
4880
4881 <listitem>
4882 <!--
4883 Author: Michael Paquier <[email protected]>
4884 Branch: master [93b76db0a] 2026-03-23 18:13:56 +0900
4885 Branch: REL_18_STABLE [882bdcf9f] 2026-03-23 18:14:28 +0900
4886 -->
4887 <para>
4888 Make the <structname>pg_aios</structname> system
4889 view's <structfield>pid</structfield> column show NULL not
4890 0 when an entry has no owning process (ChangAo Chen)
4891 <ulink url="&commit_baseurl;882bdcf9f">&sect;</ulink>
4892 </para>
4893 </listitem>
4894
4895 <listitem>
4896 <!--
4897 Author: Fujii Masao <[email protected]>
4898 Branch: master [eef1ba704] 2026-03-26 20:49:31 +0900
4899 Branch: REL_18_STABLE [98e96e579] 2026-03-26 20:50:22 +0900
4900 Branch: REL_17_STABLE [fdce5de55] 2026-03-26 20:50:27 +0900
4901 Branch: REL_16_STABLE [f42105001] 2026-03-26 20:50:33 +0900
4902 Branch: REL_15_STABLE [246c296f0] 2026-03-26 20:50:38 +0900
4903 Branch: REL_14_STABLE [bf7ecf353] 2026-03-26 20:50:43 +0900
4904 -->
4905 <para>
4906 Fix premature NULL lag reporting
4907 in <structname>pg_stat_replication</structname> (Shinya Kato)
4908 <ulink url="&commit_baseurl;98e96e579">&sect;</ulink>
4909 </para>
4910
4911 <para>
4912 The lag columns frequently read as NULL even while replication
4913 activity was happening.
4914 </para>
4915 </listitem>
4916
4917 <listitem>
4918 <!--
4919 Author: Peter Geoghegan <[email protected]>
4920 Branch: master [748d871b7] 2026-04-29 11:22:23 -0400
4921 Branch: REL_18_STABLE [1e71970d2] 2026-04-29 11:22:21 -0400
4922 -->
4923 <para>
4924 Fix under-allocation of shared memory used for parallel btree index
4925 scans (Siddharth Kothari)
4926 <ulink url="&commit_baseurl;1e71970d2">&sect;</ulink>
4927 </para>
4928
4929 <para>
4930 In edge cases this could result in a server crash.
4931 </para>
4932 </listitem>
4933
4934 <listitem>
4935 <!--
4936 Author: Tomas Vondra <[email protected]>
4937 Branch: master [b1f14c967] 2026-03-13 23:25:24 +0100
4938 Branch: REL_18_STABLE [5b3f63a1b] 2026-03-13 23:26:02 +0100
4939 Branch: REL_17_STABLE [6ef36bb35] 2026-03-13 23:26:15 +0100
4940 Branch: REL_16_STABLE [4f4025eac] 2026-03-13 23:26:25 +0100
4941 Branch: REL_15_STABLE [ce06b5740] 2026-03-13 23:26:36 +0100
4942 Branch: REL_14_STABLE [c0ffc725f] 2026-03-13 23:26:49 +0100
4943 -->
4944 <para>
4945 Avoid rare flush failure when working with non-WAL-logged GiST
4946 indexes (Tomas Vondra)
4947 <ulink url="&commit_baseurl;5b3f63a1b">&sect;</ulink>
4948 </para>
4949
4950 <para>
4951 A non-logged GiST index could nonetheless sometimes
4952 produce <quote>xlog flush request <replaceable>n/nnnn</replaceable>
4953 is not satisfied</quote> errors, due to incorrect selection of
4954 a <quote>fake LSN</quote> to represent an insertion point.
4955 </para>
4956 </listitem>
4957
4958 <listitem>
4959 <!--
4960 Author: Michael Paquier <[email protected]>
4961 Branch: master [4da2afd01] 2026-03-09 13:46:27 +0900
4962 Branch: REL_18_STABLE [a0f38604d] 2026-03-09 13:46:31 +0900
4963 Branch: REL_17_STABLE [2543b9ea9] 2026-03-09 13:46:33 +0900
4964 Branch: REL_16_STABLE [0af5e64e9] 2026-03-09 13:46:35 +0900
4965 Branch: REL_15_STABLE [46c93b705] 2026-03-09 13:46:37 +0900
4966 Branch: REL_14_STABLE [eb11d7a91] 2026-03-09 13:46:38 +0900
4967 -->
4968 <para>
4969 Fix underestimate of required size of DSA page maps for odd-size
4970 segments (Paul Bunn)
4971 <ulink url="&commit_baseurl;a0f38604d">&sect;</ulink>
4972 </para>
4973
4974 <para>
4975 This miscalculation led to out-of-bounds accesses and hence server
4976 crashes.
4977 </para>
4978 </listitem>
4979
4980 <listitem>
4981 <!--
4982 Author: Heikki Linnakangas <[email protected]>
4983 Branch: master [ccae90abd] 2026-03-02 19:19:22 +0200
4984 Branch: REL_18_STABLE [0a50ef094] 2026-03-02 19:19:26 +0200
4985 Branch: REL_17_STABLE [dcd9c06a4] 2026-03-02 19:19:29 +0200
4986 Branch: master [fe08113ae] 2026-03-04 11:29:02 +0200
4987 Branch: REL_18_STABLE [fa3b328e6] 2026-03-04 11:30:03 +0200
4988 Branch: REL_17_STABLE [969576dab] 2026-03-04 11:30:06 +0200
4989 -->
4990 <para>
4991 Fix indexing of oldest-multixact arrays in shared memory
4992 (Yura Sokolov)
4993 <ulink url="&commit_baseurl;0a50ef094">&sect;</ulink>
4994 <ulink url="&commit_baseurl;fa3b328e6">&sect;</ulink>
4995 </para>
4996
4997 <para>
4998 This mistake could cause a prepared-but-not-yet-committed
4999 transaction's row locks to appear invisible to other sessions, or
5000 other visibility issues for the results of such a transaction.
5001 With a very small max_connections setting, memory stomps were also
5002 possible.
5003 </para>
5004 </listitem>
5005
5006 <listitem>
5007 <!--
5008 Author: Michael Paquier <[email protected]>
5009 Branch: master [f7dc17aa9] 2026-03-02 13:14:15 +0900
5010 Branch: REL_18_STABLE [730c98d03] 2026-03-02 13:14:18 +0900
5011 -->
5012 <para>
5013 Fix array overrun when too many <command>EXPLAIN</command> extension
5014 options are installed (Joel Jacobson)
5015 <ulink url="&commit_baseurl;730c98d03">&sect;</ulink>
5016 </para>
5017 </listitem>
5018
5019 <listitem>
5020 <!--
5021 Author: Michael Paquier <[email protected]>
5022 Branch: master [3b7a6fa15] 2026-03-02 09:38:37 +0900
5023 Branch: REL_18_STABLE [83671c0da] 2026-03-02 09:38:40 +0900
5024 Branch: REL_17_STABLE [530b6b02f] 2026-03-02 09:38:42 +0900
5025 Branch: REL_16_STABLE [04745ba9c] 2026-03-02 09:38:44 +0900
5026 Branch: REL_15_STABLE [f033abc6c] 2026-03-02 09:38:46 +0900
5027 Branch: REL_14_STABLE [038c7d4a3] 2026-03-02 09:38:47 +0900
5028 -->
5029 <para>
5030 Fix possible server crash when processing extended statistics on
5031 expressions of extension data types (Michael Paquier)
5032 <ulink url="&commit_baseurl;83671c0da">&sect;</ulink>
5033 </para>
5034
5035 <para>
5036 NULL pointer dereferences were possible if the data type's
5037 typanalyze function does not compute any useful statistics.
5038 No in-core typanalyze function behaves that way, but extensions
5039 could.
5040 </para>
5041 </listitem>
5042
5043 <listitem>
5044 <!--
5045 Author: Tom Lane <[email protected]>
5046 Branch: master [98616ac18] 2026-02-27 12:54:02 -0500
5047 Branch: REL_18_STABLE [c2c1962a6] 2026-02-27 12:54:02 -0500
5048 -->
5049 <para>
5050 Correctly display join alias Vars that are used in <literal>GROUP
5051 BY</literal> (Tom Lane)
5052 <ulink url="&commit_baseurl;c2c1962a6">&sect;</ulink>
5053 </para>
5054
5055 <para>
5056 In views containing queries like <literal>SELECT ... t1 LEFT JOIN t2
5057 USING (x) GROUP BY x</literal>, the <literal>GROUP BY</literal>
5058 clause could be displayed incorrectly by deparsing, leading to
5059 dump/restore failures. Failures occurred only
5060 if <literal>t1.x</literal> and <literal>t2.x</literal> were not of
5061 identical data types and <literal>t1.x</literal> was the side that
5062 required an implicit coercion.
5063 </para>
5064 </listitem>
5065
5066 <listitem>
5067 <!--
5068 Author: Jeff Davis <[email protected]>
5069 Branch: master [d942511f0] 2026-02-26 12:15:01 -0800
5070 Branch: REL_18_STABLE [4abf63c62] 2026-02-26 12:15:15 -0800
5071 Branch: REL_17_STABLE [4761f2eee] 2026-02-26 12:15:23 -0800
5072 Branch: REL_16_STABLE [a4515c9b4] 2026-02-26 12:15:31 -0800
5073 -->
5074 <para>
5075 Fix minor memory leaks in ICU-based string processing (Jeff Davis)
5076 <ulink url="&commit_baseurl;4abf63c62">&sect;</ulink>
5077 </para>
5078 </listitem>
5079
5080 <listitem>
5081 <!--
5082 Author: Michael Paquier <[email protected]>
5083 Branch: master [9b43e6793] 2026-04-21 09:39:59 +0900
5084 Branch: REL_18_STABLE [affdb2dd5] 2026-04-21 09:40:03 +0900
5085 Branch: REL_17_STABLE [e381843cf] 2026-04-21 09:40:04 +0900
5086 Branch: REL_16_STABLE [2d347f2cd] 2026-04-21 09:40:06 +0900
5087 Branch: REL_15_STABLE [23cebf672] 2026-04-21 09:40:07 +0900
5088 -->
5089 <para>
5090 If the startup process fails, properly shut down other child
5091 processes before exiting the postmaster (Ayush Tiwari)
5092 <ulink url="&commit_baseurl;affdb2dd5">&sect;</ulink>
5093 </para>
5094
5095 <para>
5096 The handling of this situation relied on a long-obsolete assumption
5097 that no other postmaster children exist while the startup process is
5098 running, so that immediate postmaster exit is acceptable.
5099 Orphaned children would eventually notice the postmaster's death and
5100 exit on their own, but a cleaner shutdown procedure is desirable.
5101 </para>
5102 </listitem>
5103
5104 <listitem>
5105 <!--
5106 Author: Heikki Linnakangas <[email protected]>
5107 Branch: REL_18_STABLE [0852643e1] 2026-03-23 11:53:32 +0200
5108 Branch: REL_17_STABLE [1ca385032] 2026-03-23 11:59:07 +0200
5109 Branch: REL_16_STABLE [77dff5d93] 2026-03-23 12:02:27 +0200
5110 Branch: REL_15_STABLE [a5f412107] 2026-03-23 12:02:35 +0200
5111 Branch: REL_14_STABLE [e35e466f6] 2026-03-23 12:03:30 +0200
5112 -->
5113 <para>
5114 Fix race condition between WAL replay of checkpoints and multixact
5115 ID creations (Heikki Linnakangas)
5116 <ulink url="&commit_baseurl;0852643e1">&sect;</ulink>
5117 </para>
5118
5119 <para>
5120 A standby server following WAL from a primary of an older minor
5121 version could get into a crash-and-restart loop complaining
5122 about <quote>could not access status of transaction</quote>.
5123 </para>
5124 </listitem>
5125
5126 <listitem>
5127 <!--
5128 Author: Fujii Masao <[email protected]>
5129 Branch: master [6eedb2a5f] 2026-03-06 16:43:40 +0900
5130 Branch: REL_18_STABLE [3eb2fecdb] 2026-03-06 16:44:40 +0900
5131 Branch: REL_17_STABLE [bbbc0888b] 2026-03-06 16:44:45 +0900
5132 Branch: REL_16_STABLE [82935467a] 2026-03-06 16:44:51 +0900
5133 Branch: REL_15_STABLE [42734f296] 2026-03-06 16:44:59 +0900
5134 Branch: REL_14_STABLE [3bf6f22ce] 2026-03-06 16:45:05 +0900
5135 Branch: master [d927b4bd9] 2026-03-17 08:10:20 +0900
5136 Branch: REL_18_STABLE [980498138] 2026-03-17 08:12:25 +0900
5137 Branch: REL_17_STABLE [8ee536c89] 2026-03-17 08:12:32 +0900
5138 Branch: REL_16_STABLE [da21ecf57] 2026-03-17 08:12:37 +0900
5139 Branch: REL_15_STABLE [fa9f2e317] 2026-03-17 08:12:41 +0900
5140 Branch: REL_14_STABLE [f15471464] 2026-03-17 08:12:46 +0900
5141 -->
5142 <para>
5143 Prevent indefinite wait in shutdown of a walsender process
5144 (Anthonin Bonnefoy)
5145 <ulink url="&commit_baseurl;3eb2fecdb">&sect;</ulink>
5146 <ulink url="&commit_baseurl;980498138">&sect;</ulink>
5147 </para>
5148
5149 <para>
5150 At shutdown of a cluster that is publishing logical replication
5151 data, the walsender waits for all pending WAL to be written out.
5152 But it did not correctly request that to happen, so that in some
5153 cases this could become an indefinite wait.
5154 </para>
5155 </listitem>
5156
5157 <listitem>
5158 <!--
5159 Author: Alexander Korotkov <[email protected]>
5160 Branch: master [c06d1a4ba] 2026-05-03 20:23:50 +0300
5161 Branch: REL_18_STABLE [ac3b97db3] 2026-05-03 20:27:36 +0300
5162 Branch: REL_17_STABLE [1cf010f21] 2026-05-03 20:27:33 +0300
5163 Branch: REL_16_STABLE [54537de35] 2026-05-03 20:27:02 +0300
5164 Branch: REL_15_STABLE [ca259b084] 2026-05-03 20:26:55 +0300
5165 Branch: REL_14_STABLE [f5d1038d9] 2026-05-03 20:26:07 +0300
5166 -->
5167 <para>
5168 Ensure that changes to tables' free space maps are persisted during
5169 recovery (Alexey Makhmutov)
5170 <ulink url="&commit_baseurl;ac3b97db3">&sect;</ulink>
5171 </para>
5172
5173 <para>
5174 Previously, while WAL replay did update the free space map while
5175 replaying operations that should change it, the map page buffer did
5176 not get marked dirty if checksums are enabled, so that the changes
5177 might never get written out. On a standby server, over time this
5178 would result in a map wildly at variance with the table's actual
5179 contents. While the map is only used as a hint, this condition
5180 could cause significant performance degradation for some period of
5181 time after the standby server is promoted to be active, until most
5182 of the map has been repaired by updates.
5183 </para>
5184 </listitem>
5185
5186 <listitem>
5187 <!--
5188 Author: Andrew Dunstan <[email protected]>
5189 Branch: master [c34a280c8] 2026-05-01 15:12:28 -0400
5190 Branch: REL_18_STABLE [e2688ea5e] 2026-05-01 15:15:15 -0400
5191 Branch: REL_17_STABLE [5d67549d9] 2026-05-01 15:15:23 -0400
5192 Branch: REL_16_STABLE [7e4c871f4] 2026-05-01 15:15:33 -0400
5193 Branch: REL_15_STABLE [6916f4410] 2026-05-01 15:16:02 -0400
5194 Branch: REL_14_STABLE [f0e3f9732] 2026-05-01 15:16:42 -0400
5195 -->
5196 <para>
5197 Fix crashes in some <application>ecpg</application> functions when
5198 called without any established connection (Shruthi Gowda)
5199 <ulink url="&commit_baseurl;e2688ea5e">&sect;</ulink>
5200 </para>
5201 </listitem>
5202
5203 <listitem>
5204 <!--
5205 Author: Tom Lane <[email protected]>
5206 Branch: master [bc30c704a] 2026-04-02 12:20:36 -0400
5207 Branch: REL_18_STABLE [698eae7db] 2026-04-02 12:20:26 -0400
5208 -->
5209 <para>
5210 Harden tar-file parsing logic against archives it can't handle
5211 (Tom Lane)
5212 <ulink url="&commit_baseurl;698eae7db">&sect;</ulink>
5213 </para>
5214
5215 <para>
5216 The tar-file reading code used
5217 in <application>pg_basebackup</application>
5218 and <application>pg_verifybackup</application> failed to verify that
5219 the input is a tar file at all, let alone that it fits into the
5220 subset of valid tar files that we can handle. This isn't a problem
5221 for the normal scenario where the input file was generated
5222 by <productname>PostgreSQL</productname> code, but it can be an
5223 issue if the input has been generated by some
5224 other <application>tar</application> program.
5225 </para>
5226 </listitem>
5227
5228 <listitem>
5229 <!--
5230 Author: Andrew Dunstan <[email protected]>
5231 Branch: master [01d58d7e3] 2026-03-29 09:01:47 -0400
5232 Branch: REL_18_STABLE [5095f3f4a] 2026-03-29 09:02:15 -0400
5233 Branch: REL_17_STABLE [f1298a4c2] 2026-03-29 09:11:37 -0400
5234 Branch: REL_16_STABLE [1590723f0] 2026-03-29 09:12:28 -0400
5235 Branch: REL_15_STABLE [d3bb7841b] 2026-03-29 09:12:40 -0400
5236 Author: Tom Lane <[email protected]>
5237 Branch: master [ac0accafd] 2026-03-05 14:43:21 -0500
5238 Branch: REL_18_STABLE [a01a592b1] 2026-03-05 14:43:21 -0500
5239 Branch: REL_17_STABLE [8b198b093] 2026-03-05 14:43:21 -0500
5240 Branch: REL_16_STABLE [cce939c71] 2026-03-05 14:43:21 -0500
5241 Branch: REL_15_STABLE [9a42888a3] 2026-03-05 14:43:21 -0500
5242 Author: Tom Lane <[email protected]>
5243 Branch: master [c70f6dc6b] 2026-03-04 12:08:37 -0500
5244 Branch: REL_18_STABLE [78dc9a808] 2026-03-04 12:08:37 -0500
5245 Branch: REL_17_STABLE [2640c5ba7] 2026-03-04 12:08:37 -0500
5246 Branch: REL_16_STABLE [415cc943f] 2026-03-04 12:08:37 -0500
5247 Branch: REL_15_STABLE [4548e8746] 2026-03-04 12:08:37 -0500
5248 -->
5249 <para>
5250 Fix assorted bugs in backup decompression and tar-parsing code
5251 (Andrew Dunstan, Tom Lane, Chao Li)
5252 <ulink url="&commit_baseurl;5095f3f4a">&sect;</ulink>
5253 <ulink url="&commit_baseurl;a01a592b1">&sect;</ulink>
5254 <ulink url="&commit_baseurl;78dc9a808">&sect;</ulink>
5255 </para>
5256
5257 <para>
5258 The decompression and tar-file reading code used
5259 in <application>pg_basebackup</application>
5260 and <application>pg_verifybackup</application> mishandled tar-file
5261 padding data, could corrupt LZ4-compressed data in edge cases,
5262 failed to check for some unusual error conditions, failed to exit
5263 after compression/decompression errors (leading to cascading error
5264 reports), and leaked memory.
5265 </para>
5266 </listitem>
5267
5268 <listitem>
5269 <!--
5270 Author: Álvaro Herrera <[email protected]>
5271 Branch: master [d0833fdae] 2026-02-26 11:50:26 +0100
5272 Branch: REL_18_STABLE [c3c8b63d7] 2026-02-26 11:50:26 +0100
5273 -->
5274 <para>
5275 In <application>pg_dump</application>, preserve <literal>NO
5276 INHERIT</literal> property of <literal>NOT NULL</literal>
5277 constraints (Jian He)
5278 <ulink url="&commit_baseurl;c3c8b63d7">&sect;</ulink>
5279 </para>
5280
5281 <para>
5282 Some cases missed printing the <literal>NO INHERIT</literal> clause.
5283 </para>
5284 </listitem>
5285
5286 <listitem>
5287 <!--
5288 Author: Tom Lane <[email protected]>
5289 Branch: master [74b4438a7] 2026-03-02 11:15:10 -0500
5290 Branch: REL_18_STABLE [b09158cc7] 2026-03-02 11:14:58 -0500
5291 Branch: REL_17_STABLE [1cd783d20] 2026-03-02 11:14:58 -0500
5292 Branch: REL_16_STABLE [a4649c50a] 2026-03-02 11:14:58 -0500
5293 -->
5294 <para>
5295 In <application>pg_dumpall</application>, don't skip
5296 role <literal>GRANT</literal>s with dangling grantor OIDs
5297 (Tom Lane)
5298 <ulink url="&commit_baseurl;b09158cc7">&sect;</ulink>
5299 </para>
5300
5301 <para>
5302 Instead, handle such cases by emitting <literal>GRANT</literal>
5303 without any <literal>GRANTED BY</literal> clause, as we did before
5304 v16. This avoids losing the grant in foreseeable cases, since
5305 pre-v16 servers didn't prevent dropping the grantor role. Continue
5306 to emit a warning about the missing grantor, but only if the source
5307 server is v16 or later.
5308 </para>
5309 </listitem>
5310
5311 <listitem>
5312 <!--
5313 Author: Jacob Champion <[email protected]>
5314 Branch: master [a60a10338] 2026-02-24 14:01:37 -0800
5315 Branch: REL_18_STABLE [1b2773179] 2026-02-24 14:01:41 -0800
5316 Branch: REL_17_STABLE [ad7fc3f1f] 2026-02-24 14:01:46 -0800
5317 Branch: REL_16_STABLE [a38ed212f] 2026-02-24 14:01:51 -0800
5318 Branch: REL_15_STABLE [e726620d2] 2026-02-24 14:01:54 -0800
5319 Branch: REL_14_STABLE [c47744ede] 2026-02-24 14:01:58 -0800
5320 -->
5321 <para>
5322 In <application>pg_upgrade</application>, take care to use the
5323 correct protocol version when connecting to older source servers
5324 (Jacob Champion)
5325 <ulink url="&commit_baseurl;1b2773179">&sect;</ulink>
5326 </para>
5327
5328 <para>
5329 This could be problematic when attempting to upgrade from a pre-2018
5330 server.
5331 </para>
5332 </listitem>
5333
5334 <listitem>
5335 <!--
5336 Author: Nathan Bossart <[email protected]>
5337 Branch: master [cc774c543] 2026-03-02 13:12:25 -0600
5338 Branch: REL_18_STABLE [bde9ad315] 2026-03-02 13:12:25 -0600
5339 Branch: REL_17_STABLE [f510577de] 2026-03-02 13:12:25 -0600
5340 Branch: REL_16_STABLE [28c2b7896] 2026-03-02 13:12:25 -0600
5341 Branch: REL_15_STABLE [8fc45ac5d] 2026-03-02 13:12:25 -0600
5342 -->
5343 <para>
5344 In <filename>contrib/basic_archive</filename>, allow the archive
5345 directory to be missing at startup (Nathan Bossart)
5346 <ulink url="&commit_baseurl;bde9ad315">&sect;</ulink>
5347 </para>
5348
5349 <para>
5350 Previously, the setting
5351 of <literal>basic_archive.archive_directory</literal> was rejected
5352 if it didn't point to an existing directory. This is undesirable
5353 because archiving will be stuck indefinitely, even if the directory
5354 appears later.
5355 </para>
5356 </listitem>
5357
5358 <listitem>
5359 <!--
5360 Author: Jeff Davis <[email protected]>
5361 Branch: master [c8308a984] 2026-02-26 12:23:22 -0800
5362 Branch: REL_18_STABLE [b3c2a3d38] 2026-02-26 12:23:51 -0800
5363 Branch: REL_18_STABLE [53a57cae1] 2026-02-26 15:19:31 -0800
5364 Branch: REL_17_STABLE [d1bd9a7dc] 2026-02-26 12:24:12 -0800
5365 Branch: REL_16_STABLE [3ed2c7ef7] 2026-02-26 12:25:00 -0800
5366 Branch: REL_15_STABLE [2b993167f] 2026-02-26 12:26:13 -0800
5367 Branch: REL_14_STABLE [058710d41] 2026-02-26 12:26:32 -0800
5368 -->
5369 <para>
5370 Fix <filename>contrib/ltree</filename> to cope when case-folding
5371 changes a string's byte length (Jeff Davis)
5372 <ulink url="&commit_baseurl;b3c2a3d38">&sect;</ulink>
5373 <ulink url="&commit_baseurl;53a57cae1">&sect;</ulink>
5374 </para>
5375
5376 <para>
5377 Previously, <type>lquery</type> patterns specifying case-insensitive
5378 matching might fail to match labels they should match.
5379 </para>
5380 </listitem>
5381
5382 <listitem>
5383 <!--
5384 Author: Amit Langote <[email protected]>
5385 Branch: master [059cf7f58] 2026-04-16 13:47:07 +0900
5386 Branch: REL_18_STABLE [6723d462d] 2026-04-16 13:49:39 +0900
5387 -->
5388 <para>
5389 Fix mis-structured output
5390 from <filename>contrib/pg_overexplain</filename>'s
5391 <literal>RANGE_TABLE</literal> option (Satyanarayana Narlapuram)
5392 <ulink url="&commit_baseurl;6723d462d">&sect;</ulink>
5393 </para>
5394
5395 <para>
5396 Some fields were misplaced in JSON, YAML, and XML formats, resulting
5397 in structurally invalid output.
5398 </para>
5399 </listitem>
5400
5401 <listitem>
5402 <!--
5403 Author: Heikki Linnakangas <[email protected]>
5404 Branch: master [3c74cb576] 2026-03-27 12:25:10 +0200
5405 Branch: REL_18_STABLE [25b02320e] 2026-03-27 12:21:29 +0200
5406 Branch: REL_17_STABLE [351e59f34] 2026-03-27 12:21:38 +0200
5407 Branch: REL_16_STABLE [52edaf9d9] 2026-03-27 12:21:48 +0200
5408 Branch: REL_15_STABLE [92cf11171] 2026-03-27 12:22:21 +0200
5409 Branch: REL_14_STABLE [a6d03067f] 2026-03-27 12:23:38 +0200
5410 -->
5411 <para>
5412 In <filename>contrib/pg_stat_statements</filename>, don't leak
5413 memory if an error occurs while parsing the
5414 <filename>pgss_query_texts.stat</filename> file (Heikki Linnakangas)
5415 <ulink url="&commit_baseurl;25b02320e">&sect;</ulink>
5416 </para>
5417 </listitem>
5418
5419 <listitem>
5420 <!--
5421 Author: Etsuro Fujita <[email protected]>
5422 Branch: master [648818ba3] 2026-05-05 18:55:00 +0900
5423 Branch: REL_18_STABLE [c318777da] 2026-05-05 18:55:02 +0900
5424 Branch: REL_17_STABLE [af8f9248f] 2026-05-05 18:55:03 +0900
5425 Branch: REL_16_STABLE [1352651c2] 2026-05-05 18:55:04 +0900
5426 Branch: REL_15_STABLE [34c18a225] 2026-05-05 18:55:05 +0900
5427 Branch: REL_14_STABLE [fd5b36ab1] 2026-05-05 18:55:06 +0900
5428 -->
5429 <para>
5430 In <filename>contrib/postgres_fdw</filename>, avoid crash due to
5431 premature cleanup of a failed connection (Etsuro Fujita)
5432 <ulink url="&commit_baseurl;c318777da">&sect;</ulink>
5433 </para>
5434
5435 <para>
5436 If a remote connection fails abort cleanup, we can't use it any
5437 longer. But delay closing the connection object until end of
5438 transaction, because there might still be references to it within
5439 data structures such as open cursors.
5440 </para>
5441 </listitem>
5442
5443 <listitem>
5444 <!--
5445 Author: Tom Lane <[email protected]>
5446 Branch: master [f64f62f5b] 2026-04-24 12:28:35 -0400
5447 Branch: REL_18_STABLE [8a431b6d6] 2026-04-24 12:28:35 -0400
5448 Branch: REL_17_STABLE [4c0eab6f0] 2026-04-24 12:28:35 -0400
5449 Branch: REL_16_STABLE [0465c999e] 2026-04-24 12:28:35 -0400
5450 Branch: REL_15_STABLE [e28fc73d5] 2026-04-24 12:28:35 -0400
5451 Branch: REL_14_STABLE [affd929c9] 2026-04-24 12:28:35 -0400
5452 -->
5453 <para>
5454 Update time zone data files to <application>tzdata</application>
5455 release 2026b (Tom Lane)
5456 <ulink url="&commit_baseurl;8a431b6d6">&sect;</ulink>
5457 </para>
5458
5459 <para>
5460 British Columbia (America/Vancouver) will be on year-round UTC-07
5461 (effectively, permanent DST) beginning in November 2026. This
5462 release assumes that their TZ abbreviation will
5463 be <literal>MST</literal> from that time forward. That seems likely
5464 to change, but it's unclear what new abbreviation will be used.
5465 Also a historical correction for Moldova: they have followed EU DST
5466 transition times since 2022.
5467 </para>
5468 </listitem>
5469
5470 </itemizedlist>
5471
5472 </sect2>
5473 </sect1>
5474
5475 <sect1 id="release-18-3">
5476 <title>Release 18.3</title>
5477
5478 <formalpara>
5479 <title>Release date:</title>
5480 <para>2026-02-26</para>
5481 </formalpara>
5482
5483 <para>
5484 This release contains a small number of fixes from 18.2.
5485 For information about new features in major release 18, see
5486 <xref linkend="release-18"/>.
5487 </para>
5488
5489 <sect2 id="release-18-3-migration">
5490 <title>Migration to Version 18.3</title>
5491
5492 <para>
5493 A dump/restore is not required for those running 18.X.
5494 </para>
5495
5496 <para>
5497 However, if you are upgrading from a version earlier than 18.2,
5498 see <xref linkend="release-18-2"/>.
5499 </para>
5500 </sect2>
5501
5502 <sect2 id="release-18-3-changes">
5503 <title>Changes</title>
5504
5505 <itemizedlist>
5506
5507 <listitem>
5508 <!--
5509 Author: Heikki Linnakangas <[email protected]>
5510 Branch: REL_18_STABLE [817f74600] 2026-02-16 17:16:59 +0200
5511 Branch: REL_17_STABLE [4a36c89f1] 2026-02-16 17:18:17 +0200
5512 Branch: REL_16_STABLE [23064542f] 2026-02-16 17:20:29 +0200
5513 Branch: REL_15_STABLE [899de38d8] 2026-02-16 17:20:51 +0200
5514 Branch: REL_14_STABLE [547a8aaa7] 2026-02-16 17:20:56 +0200
5515 -->
5516 <para>
5517 Fix failure after replaying a multixid truncation record from WAL
5518 that was generated by an older minor version (Heikki Linnakangas)
5519 <ulink url="&commit_baseurl;817f74600">&sect;</ulink>
5520 </para>
5521
5522 <para>
5523 Erroneous logic for coping with the way that previous versions
5524 handled multixid wraparound led to replay failure, with messages
5525 like <quote>could not access status of transaction</quote>.
5526 A typical scenario in which this could occur is a standby server of
5527 the latest minor version consuming WAL from a primary server of an
5528 older version.
5529 </para>
5530 </listitem>
5531
5532 <listitem>
5533 <!--
5534 Author: Noah Misch <[email protected]>
5535 Branch: master [9f4fd119b] 2026-02-14 12:16:16 -0800
5536 Branch: REL_18_STABLE [6e045e1a6] 2026-02-14 12:16:19 -0800
5537 Branch: REL_17_STABLE [5d5232bc3] 2026-02-14 12:16:20 -0800
5538 Branch: REL_16_STABLE [bdfb37228] 2026-02-14 12:16:20 -0800
5539 Branch: REL_15_STABLE [a20eb248c] 2026-02-14 12:16:21 -0800
5540 Branch: REL_14_STABLE [14b1fd617] 2026-02-14 12:16:21 -0800
5541 Branch: master [8cef93d8a] 2026-02-16 18:04:58 -0800
5542 Branch: REL_18_STABLE [d04b34d68] 2026-02-16 18:05:01 -0800
5543 Branch: REL_17_STABLE [50d361f62] 2026-02-16 18:05:02 -0800
5544 Branch: REL_16_STABLE [2280ab354] 2026-02-16 18:05:02 -0800
5545 Branch: REL_15_STABLE [ec86152e0] 2026-02-16 18:05:02 -0800
5546 Branch: REL_14_STABLE [a0769e74d] 2026-02-16 18:05:03 -0800
5547 Branch: master [4644f8b23] 2026-02-14 12:16:16 -0800
5548 Branch: REL_18_STABLE [4174e41b9] 2026-02-14 12:16:19 -0800
5549 Branch: REL_17_STABLE [8e73530f1] 2026-02-14 12:16:20 -0800
5550 Branch: REL_16_STABLE [45eb47230] 2026-02-14 12:16:20 -0800
5551 Branch: REL_15_STABLE [5b305ebcc] 2026-02-14 12:16:20 -0800
5552 Branch: REL_14_STABLE [44fc85bbf] 2026-02-14 12:16:21 -0800
5553 -->
5554 <para>
5555 Avoid incorrect complaint of invalid encoding
5556 when <function>substring()</function> is applied
5557 to <quote>toasted</quote> data (Noah Misch)
5558 <ulink url="&commit_baseurl;6e045e1a6">&sect;</ulink>
5559 <ulink url="&commit_baseurl;d04b34d68">&sect;</ulink>
5560 <ulink url="&commit_baseurl;4174e41b9">&sect;</ulink>
5561 </para>
5562
5563 <para>
5564 The fix for CVE-2026-2006 was too aggressive and could raise an
5565 error about an incomplete character in cases that are actually
5566 valid.
5567 </para>
5568 </listitem>
5569
5570 <listitem>
5571 <!--
5572 Author: Heikki Linnakangas <[email protected]>
5573 Branch: master [18bcdb75d] 2026-02-20 11:56:42 +0200
5574 Branch: REL_18_STABLE [041e02e6a] 2026-02-20 11:56:50 +0200
5575 -->
5576 <para>
5577 Fix oversight in the fix for CVE-2026-2007 (Zsolt Parragi)
5578 <ulink url="&commit_baseurl;041e02e6a">&sect;</ulink>
5579 </para>
5580
5581 <para>
5582 If the <quote>bounds</quote> array needed to be expanded, because
5583 the input contained more trigrams than the initial guess,
5584 <function>generate_trgm_only</function> didn't return the modified
5585 array pointer to its caller. That would lead to incorrect output
5586 from <function>strict_word_similarity()</function> and related
5587 functions, or in rare cases a crash. The faulty code is reached if
5588 the input string becomes longer when it's converted to lower case.
5589 The only known instances of that occur when an ICU locale is used
5590 with certain single-byte encodings.
5591 </para>
5592 </listitem>
5593
5594 <listitem>
5595 <!--
5596 Author: Tom Lane <[email protected]>
5597 Branch: master [759b03b24] 2026-02-18 14:14:44 -0500
5598 Author: Andrew Dunstan <[email protected]>
5599 Branch: REL_18_STABLE [2f6ee7b38] 2026-02-18 10:31:03 -0500
5600 -->
5601 <para>
5602 Fix the volatility marking
5603 of <function>json_strip_nulls()</function>
5604 and <function>jsonb_strip_nulls()</function> (Andrew Dunstan)
5605 <ulink url="&commit_baseurl;2f6ee7b38">&sect;</ulink>
5606 </para>
5607
5608 <para>
5609 These functions have always been considered immutable, but
5610 refactoring in version 18 accidentally marked them stable instead.
5611 That prevents their use in index expressions and could cause
5612 unnecessary repeat evaluations in queries. This fix corrects the
5613 marking in newly-initialized database clusters (including clusters
5614 that are <application>pg_upgrade</application>'d to 18.3 or later).
5615 However it will not help existing clusters made using 18.0 through
5616 18.2.
5617 </para>
5618
5619 <para>
5620 If this mistake affects your usage of these functions, the
5621 recommended fix for an existing cluster is a manual catalog update.
5622 As superuser, perform
5623 <programlisting>
5624 UPDATE pg_catalog.pg_proc SET provolatile = 'i' WHERE oid IN ('3261','3262');
5625 </programlisting>
5626 in each affected database. Update <literal>template0</literal>
5627 and <literal>template1</literal> as well, so that databases made in
5628 future will have the fix.
5629 </para>
5630 </listitem>
5631
5632 <listitem>
5633 <!--
5634 Author: Richard Guo <[email protected]>
5635 Branch: master [691977d37] 2026-02-20 17:57:53 +0900
5636 Branch: REL_18_STABLE [ed57c207c] 2026-02-20 18:00:02 +0900
5637 Branch: REL_17_STABLE [bcaf1b510] 2026-02-20 18:01:56 +0900
5638 Branch: REL_16_STABLE [ec20a4552] 2026-02-20 18:04:26 +0900
5639 -->
5640 <para>
5641 Fix computation of the set of potentially-nulling outer joins for
5642 the output of a <literal>LATERAL UNION ALL</literal> subquery
5643 (Richard Guo)
5644 <ulink url="&commit_baseurl;ed57c207c">&sect;</ulink>
5645 </para>
5646
5647 <para>
5648 This error could lead to skipping <literal>NOT NULL</literal> tests
5649 in the mistaken belief that they were unnecessary, resulting in
5650 wrong query output.
5651 </para>
5652 </listitem>
5653
5654 <listitem>
5655 <!--
5656 Author: Álvaro Herrera <[email protected]>
5657 Branch: master [0eeffd31b] 2026-02-21 12:22:08 +0100
5658 Branch: REL_18_STABLE [8d9a97e0b] 2026-02-21 12:22:08 +0100
5659 -->
5660 <para>
5661 Avoid name collisions between user-written constraints and
5662 automatically-named <literal>NOT NULL</literal> constraints
5663 (Laurenz Albe)
5664 <ulink url="&commit_baseurl;8d9a97e0b">&sect;</ulink>
5665 </para>
5666
5667 <para>
5668 As of version 18, <literal>NOT NULL</literal> constraints have
5669 full-fledged <structname>pg_constraint</structname> entries, and
5670 therefore require names. The logic for choosing a name for an
5671 unnamed <literal>NOT NULL</literal> constraint failed to avoid
5672 conflicts with user-written constraints elsewhere in the
5673 same <command>CREATE TABLE</command> statement.
5674 </para>
5675 </listitem>
5676
5677 <listitem>
5678 <!--
5679 Author: Heikki Linnakangas <[email protected]>
5680 Branch: master [78a5e3074] 2026-02-11 18:50:57 +0200
5681 Branch: REL_18_STABLE [53463b4b2] 2026-02-11 18:51:06 +0200
5682 Branch: REL_17_STABLE [842473337] 2026-02-11 18:51:12 +0200
5683 Branch: REL_16_STABLE [2332911ae] 2026-02-11 18:51:19 +0200
5684 Branch: REL_15_STABLE [ebc53ca7b] 2026-02-11 18:51:25 +0200
5685 Branch: REL_14_STABLE [82b495cdd] 2026-02-11 18:51:32 +0200
5686 -->
5687 <para>
5688 Fix <function>pg_stat_get_backend_wait_event()</function>
5689 and <function>pg_stat_get_backend_wait_event_type()</function>
5690 to report values for auxiliary processes (Heikki Linnakangas)
5691 <ulink url="&commit_baseurl;53463b4b2">&sect;</ulink>
5692 </para>
5693
5694 <para>
5695 Previously these functions returned NULL for auxiliary processes,
5696 but that's inconsistent with
5697 the <structname>pg_stat_activity</structname> view.
5698 </para>
5699 </listitem>
5700
5701 <listitem>
5702 <!--
5703 Author: Tom Lane <[email protected]>
5704 Branch: master [9863c9075] 2026-02-11 16:53:14 -0500
5705 Branch: REL_18_STABLE [ce4b7e3a1] 2026-02-11 16:53:14 -0500
5706 Branch: REL_17_STABLE [dfd850980] 2026-02-11 16:53:14 -0500
5707 Branch: REL_16_STABLE [c66f4cff1] 2026-02-11 16:53:14 -0500
5708 Branch: REL_15_STABLE [254b15cbf] 2026-02-11 16:53:14 -0500
5709 Branch: REL_14_STABLE [2b93d3820] 2026-02-11 16:53:14 -0500
5710 -->
5711 <para>
5712 Fix casting a composite-type variable to a domain type when
5713 returning its value from a PL/pgSQL function (Tom Lane)
5714 <ulink url="&commit_baseurl;ce4b7e3a1">&sect;</ulink>
5715 </para>
5716
5717 <para>
5718 If the variable's value is NULL, a <quote>cache lookup failed for
5719 type 0</quote> error resulted.
5720 </para>
5721 </listitem>
5722
5723 <listitem>
5724 <!--
5725 Author: Michael Paquier <[email protected]>
5726 Branch: master [a6f823e77] 2026-02-17 08:41:26 +0900
5727 Branch: REL_18_STABLE [4a0843c53] 2026-02-17 08:41:30 +0900
5728 Branch: REL_17_STABLE [0dfbe42da] 2026-02-17 08:41:32 +0900
5729 Branch: REL_16_STABLE [31d0b917d] 2026-02-17 08:41:34 +0900
5730 Branch: REL_15_STABLE [63c05e03b] 2026-02-17 08:41:35 +0900
5731 Branch: REL_14_STABLE [f604cc695] 2026-02-17 08:41:37 +0900
5732 -->
5733 <para>
5734 Fix potential null pointer dereference
5735 in <filename>contrib/hstore</filename>'s binary input function
5736 (Michael Paquier)
5737 <ulink url="&commit_baseurl;4a0843c53">&sect;</ulink>
5738 </para>
5739
5740 <para>
5741 <type>hstore</type>'s receive function crashed on input containing
5742 duplicate keys. <type>hstore</type> values generated by Postgres
5743 would never contain duplicate keys, so this mistake has gone
5744 unnoticed. The crash could be provoked by malicious or corrupted
5745 data.
5746 </para>
5747 </listitem>
5748
5749 </itemizedlist>
5750
5751 </sect2>
5752 </sect1>
5753
5754 <sect1 id="release-18-2">
5755 <title>Release 18.2</title>
5756
5757 <formalpara>
5758 <title>Release date:</title>
5759 <para>2026-02-12</para>
5760 </formalpara>
5761
5762 <para>
5763 This release contains a variety of fixes from 18.1.
5764 For information about new features in major release 18, see
5765 <xref linkend="release-18"/>.
5766 </para>
5767
5768 <sect2 id="release-18-2-migration">
5769 <title>Migration to Version 18.2</title>
5770
5771 <para>
5772 A dump/restore is not required for those running 18.X.
5773 </para>
5774
5775 <para>
5776 However, if you have any indexes on <type>ltree</type> columns, it may
5777 be necessary to reindex them after updating. See the sixth changelog
5778 entry below.
5779 </para>
5780 </sect2>
5781
5782 <sect2 id="release-18-2-changes">
5783 <title>Changes</title>
5784
5785 <itemizedlist>
5786
5787 <listitem>
5788 <!--
5789 Author: Tom Lane <[email protected]>
5790 Branch: master [60e7ae41a] 2026-02-09 09:57:43 -0500
5791 Branch: REL_18_STABLE [3b6588cd9] 2026-02-09 09:57:44 -0500
5792 Branch: REL_17_STABLE [3d160401b] 2026-02-09 09:57:44 -0500
5793 Branch: REL_16_STABLE [595956fc7] 2026-02-09 09:57:44 -0500
5794 Branch: REL_15_STABLE [429aeaebd] 2026-02-09 09:57:44 -0500
5795 Branch: REL_14_STABLE [b39d38139] 2026-02-09 09:57:44 -0500
5796 -->
5797 <para>
5798 Guard against unexpected dimensions
5799 of <type>oidvector</type>/<type>int2vector</type> (Tom Lane)
5800 <ulink url="&commit_baseurl;3b6588cd9">&sect;</ulink>
5801 </para>
5802
5803 <para>
5804 These data types are expected to be 1-dimensional arrays containing
5805 no nulls, but there are cast pathways that permit violating those
5806 expectations. Add checks to some functions that were depending on
5807 those expectations without verifying them, and could misbehave in
5808 consequence.
5809 </para>
5810
5811 <para>
5812 The <productname>PostgreSQL</productname> Project thanks
5813 Altan Birler for reporting this problem.
5814 (CVE-2026-2003)
5815 </para>
5816 </listitem>
5817
5818 <listitem>
5819 <!--
5820 Author: Tom Lane <[email protected]>
5821 Branch: master [841d42cc4] 2026-02-09 10:07:31 -0500
5822 Branch: REL_18_STABLE [66ddac698] 2026-02-09 10:07:31 -0500
5823 Branch: REL_17_STABLE [bbf5bcf58] 2026-02-09 10:07:31 -0500
5824 Branch: REL_16_STABLE [91d7c0bfd] 2026-02-09 10:07:31 -0500
5825 Branch: REL_15_STABLE [b764b26f2] 2026-02-09 10:07:31 -0500
5826 Branch: REL_14_STABLE [ea3bf3498] 2026-02-09 10:07:31 -0500
5827 Author: Tom Lane <[email protected]>
5828 Branch: master [8ebdf41c2] 2026-02-09 10:14:22 -0500
5829 Branch: REL_18_STABLE [b69af3dda] 2026-02-09 10:14:22 -0500
5830 Branch: REL_17_STABLE [dd3ad2a4d] 2026-02-09 10:14:22 -0500
5831 Branch: REL_16_STABLE [c0887b39d] 2026-02-09 10:14:22 -0500
5832 Branch: REL_15_STABLE [deb464a40] 2026-02-09 10:14:22 -0500
5833 Branch: REL_14_STABLE [7e82d9a04] 2026-02-09 10:14:22 -0500
5834 Author: Tom Lane <[email protected]>
5835 Branch: REL_17_STABLE [dbb09fd8e] 2026-02-09 10:02:23 -0500
5836 Branch: REL_16_STABLE [d484bc260] 2026-02-09 10:02:23 -0500
5837 Branch: REL_15_STABLE [3ecc84cce] 2026-02-09 10:02:23 -0500
5838 Branch: REL_14_STABLE [9fa38c572] 2026-02-09 10:02:23 -0500
5839 -->
5840 <para>
5841 Harden selectivity estimators against being attached to operators
5842 that accept unexpected data types (Tom Lane)
5843 <ulink url="&commit_baseurl;66ddac698">&sect;</ulink>
5844 <ulink url="&commit_baseurl;b69af3dda">&sect;</ulink>
5845 </para>
5846
5847 <para>
5848 <filename>contrib/intarray</filename> contained a selectivity
5849 estimation function that could be abused for arbitrary code
5850 execution, because it did not check that its input was of the
5851 expected data type. Third-party extensions should check for similar
5852 hazards and add defenses using the technique intarray now uses.
5853 Since such extension fixes will take time, we now require superuser
5854 privilege to attach a non-built-in selectivity estimator to an
5855 operator.
5856 </para>
5857
5858 <para>
5859 The <productname>PostgreSQL</productname> Project thanks
5860 Daniel Firer, as part of zeroday.cloud, for reporting this problem.
5861 (CVE-2026-2004)
5862 </para>
5863 </listitem>
5864
5865 <listitem>
5866 <!--
5867 Author: Michael Paquier <[email protected]>
5868 Branch: master [379695d3c] 2026-02-09 08:00:59 +0900
5869 Branch: REL_18_STABLE [209f387b8] 2026-02-09 08:01:05 +0900
5870 Branch: REL_17_STABLE [7a7d9693c] 2026-02-09 08:01:07 +0900
5871 Branch: REL_16_STABLE [527b730f4] 2026-02-09 08:01:09 +0900
5872 Branch: REL_15_STABLE [9a9982ec6] 2026-02-09 08:01:10 +0900
5873 Branch: REL_14_STABLE [01de2e32d] 2026-02-09 08:01:12 +0900
5874 -->
5875 <para>
5876 Fix buffer overrun in <filename>contrib/pgcrypto</filename>'s
5877 PGP decryption functions (Michael Paquier)
5878 <ulink url="&commit_baseurl;209f387b8">&sect;</ulink>
5879 </para>
5880
5881 <para>
5882 Decrypting a crafted message with an overlength session key caused a
5883 buffer overrun, with consequences as bad as arbitrary code
5884 execution.
5885 </para>
5886
5887 <para>
5888 The <productname>PostgreSQL</productname> Project thanks
5889 Team Xint Code, as part of zeroday.cloud, for reporting this problem.
5890 (CVE-2026-2005)
5891 </para>
5892 </listitem>
5893
5894 <listitem>
5895 <!--
5896 Author: Thomas Munro <[email protected]>
5897 Branch: master [af79c30dc] 2026-02-09 12:08:58 +1300
5898 Branch: REL_18_STABLE [df0852fe0] 2026-02-09 12:12:29 +1300
5899 Branch: REL_17_STABLE [838248b1b] 2026-02-09 12:23:45 +1300
5900 Branch: REL_16_STABLE [70ff9ede5] 2026-02-09 12:28:01 +1300
5901 Branch: REL_15_STABLE [b2c81ac86] 2026-02-09 12:34:12 +1300
5902 Branch: REL_14_STABLE [2a53db21e] 2026-02-09 12:38:07 +1300
5903 Branch: master [74ee636cc] 2026-02-09 12:08:58 +1300
5904 Branch: REL_18_STABLE [efef05ba9] 2026-02-09 12:12:33 +1300
5905 Branch: REL_17_STABLE [7a522039f] 2026-02-09 12:23:51 +1300
5906 Branch: REL_16_STABLE [b0e3f5cf9] 2026-02-09 12:28:07 +1300
5907 Branch: REL_15_STABLE [50863be0b] 2026-02-09 12:34:17 +1300
5908 Branch: REL_14_STABLE [6ed116046] 2026-02-09 12:38:12 +1300
5909 Branch: master [1e7fe06c1] 2026-02-09 12:44:04 +1300
5910 Branch: REL_18_STABLE [7b5fc85be] 2026-02-09 12:43:42 +1300
5911 Branch: REL_17_STABLE [319e8a644] 2026-02-09 12:42:47 +1300
5912 Branch: REL_16_STABLE [d837fb029] 2026-02-09 12:29:15 +1300
5913 Branch: REL_15_STABLE [fd82ddb67] 2026-02-09 12:34:24 +1300
5914 Branch: REL_14_STABLE [cecedb912] 2026-02-09 12:39:01 +1300
5915 Branch: master [c67bef3f3] 2026-02-09 12:44:12 +1300
5916 Branch: REL_18_STABLE [b0f5d25bc] 2026-02-09 12:43:50 +1300
5917 Branch: REL_17_STABLE [10ebc4bd6] 2026-02-09 12:42:59 +1300
5918 Branch: REL_16_STABLE [4c08960d9] 2026-02-09 12:29:41 +1300
5919 Branch: REL_15_STABLE [757bf8145] 2026-02-09 12:35:19 +1300
5920 Branch: REL_14_STABLE [e7591254c] 2026-02-09 12:39:16 +1300
5921 Author: Noah Misch <[email protected]>
5922 Branch: master [d536aee55] 2026-02-09 06:14:47 -0800
5923 Branch: REL_18_STABLE [b42709194] 2026-02-09 06:14:50 -0800
5924 Branch: REL_17_STABLE [dc072a09a] 2026-02-09 06:14:51 -0800
5925 Branch: REL_16_STABLE [0c33d5608] 2026-02-09 06:14:51 -0800
5926 Branch: REL_15_STABLE [8f8b1ffac] 2026-02-09 06:14:52 -0800
5927 Branch: REL_14_STABLE [8373ed094] 2026-02-09 06:14:52 -0800
5928 Branch: master [c5dc75479] 2026-02-09 09:08:10 -0800
5929 Branch: REL_18_STABLE [4543b02af] 2026-02-09 09:08:13 -0800
5930 Branch: REL_17_STABLE [955433ebd] 2026-02-09 09:08:13 -0800
5931 Branch: REL_16_STABLE [763671b74] 2026-02-09 09:08:13 -0800
5932 Branch: REL_15_STABLE [6f741bcb6] 2026-02-09 09:08:14 -0800
5933 Branch: REL_14_STABLE [5301b2b7d] 2026-02-09 09:08:14 -0800
5934 -->
5935 <para>
5936 Fix inadequate validation of multibyte character lengths
5937 (Thomas Munro, Noah Misch)
5938 <ulink url="&commit_baseurl;df0852fe0">&sect;</ulink>
5939 <ulink url="&commit_baseurl;efef05ba9">&sect;</ulink>
5940 <ulink url="&commit_baseurl;7b5fc85be">&sect;</ulink>
5941 <ulink url="&commit_baseurl;b0f5d25bc">&sect;</ulink>
5942 <ulink url="&commit_baseurl;b42709194">&sect;</ulink>
5943 <ulink url="&commit_baseurl;4543b02af">&sect;</ulink>
5944 </para>
5945
5946 <para>
5947 Assorted bugs allowed an attacker able to issue crafted SQL to
5948 overrun string buffers, with consequences as bad as arbitrary code
5949 execution. After these fixes, applications may
5950 observe <quote>invalid byte sequence for encoding</quote> errors
5951 when string functions process invalid text that has been stored in
5952 the database.
5953 </para>
5954
5955 <para>
5956 The <productname>PostgreSQL</productname> Project thanks Paul Gerste
5957 and Moritz Sanft, as part of zeroday.cloud, for reporting this
5958 problem.
5959 (CVE-2026-2006)
5960 </para>
5961 </listitem>
5962
5963 <listitem>
5964 <!--
5965 Author: Heikki Linnakangas <[email protected]>
5966 Branch: master [00896ddaf] 2026-02-09 12:08:58 +1300
5967 Branch: REL_18_STABLE [e0965fb1a] 2026-02-09 12:12:24 +1300
5968 Author: Heikki Linnakangas <[email protected]>
5969 Branch: master [54598670f] 2026-02-09 12:08:58 +1300
5970 Branch: REL_18_STABLE [18548681d] 2026-02-09 12:12:18 +1300
5971 -->
5972 <para>
5973 Harden <filename>contrib/pg_trgm</filename> against changes in
5974 string lowercasing behavior (Heikki Linnakangas)
5975 <ulink url="&commit_baseurl;e0965fb1a">&sect;</ulink>
5976 <ulink url="&commit_baseurl;18548681d">&sect;</ulink>
5977 </para>
5978
5979 <para>
5980 Fix potential buffer overruns arising from the fact that in some
5981 locales lower-casing a string can produce more characters (not
5982 bytes) than were in the original. That behavior is new in version
5983 18, and so is the bug.
5984 </para>
5985
5986 <para>
5987 The <productname>PostgreSQL</productname> Project thanks
5988 Heikki Linnakangas for reporting this problem.
5989 (CVE-2026-2007)
5990 </para>
5991 </listitem>
5992
5993 <listitem>
5994 <!--
5995 Author: Jeff Davis <[email protected]>
5996 Branch: master [7f007e4a0] 2025-12-16 12:57:00 -0800
5997 Branch: REL_18_STABLE [806555e30] 2025-12-16 12:57:12 -0800
5998 Branch: REL_18_STABLE [8993bf099] 2026-01-27 08:16:07 -0800
5999 -->
6000 <para>
6001 Fix inconsistent case-insensitive matching
6002 in <filename>contrib/ltree</filename> (Jeff Davis)
6003 <ulink url="&commit_baseurl;806555e30">&sect;</ulink>
6004 <ulink url="&commit_baseurl;8993bf099">&sect;</ulink>
6005 </para>
6006
6007 <para>
6008 Index-related routines in <filename>ltree</filename> used a
6009 different implementation of case-folding than the primary operators
6010 did. Their behavior was equivalent only if the default collation
6011 provider was libc and the encoding was single-byte.
6012 </para>
6013
6014 <para>
6015 To fix, change the code to use case-folding with the database's
6016 default collation.
6017 This change will require reindexing indexes on <type>ltree</type>
6018 columns (regardless of the index access method) unless the database
6019 uses libc as collation provider and its encoding is single-byte.
6020 Without that, searches of such indexes will fail to locate relevant
6021 entries.
6022 </para>
6023 </listitem>
6024
6025 <listitem>
6026 <!--
6027 Author: Álvaro Herrera <[email protected]>
6028 Branch: master [96e2af605] 2026-02-03 12:33:29 +0100
6029 Branch: REL_18_STABLE [492a69e14] 2026-02-03 12:33:29 +0100
6030 -->
6031 <para>
6032 When using <command>ALTER TABLE ... ADD CONSTRAINT</command> to add
6033 a not-null constraint with an explicit name, if the column is
6034 already marked NOT NULL, require that the provided name match the
6035 existing constraint name (Álvaro Herrera, Srinath Reddy Sadipiralla)
6036 <ulink url="&commit_baseurl;492a69e14">&sect;</ulink>
6037 </para>
6038 </listitem>
6039
6040 <listitem>
6041 <!--
6042 Author: Tom Lane <[email protected]>
6043 Branch: master [35b5c62c3] 2025-11-18 12:56:55 -0500
6044 Branch: REL_18_STABLE [12bc32917] 2025-11-18 12:56:55 -0500
6045 Branch: REL_17_STABLE [075a763e2] 2025-11-18 12:56:55 -0500
6046 Branch: REL_16_STABLE [1c8c3206f] 2025-11-18 12:56:55 -0500
6047 Branch: REL_15_STABLE [9f5a58aac] 2025-11-18 12:56:55 -0500
6048 Branch: REL_14_STABLE [b85397481] 2025-11-18 12:56:55 -0500
6049 -->
6050 <para>
6051 Don't allow CTE references in sub-selects to determine semantic
6052 levels of aggregate functions (Tom Lane)
6053 <ulink url="&commit_baseurl;12bc32917">&sect;</ulink>
6054 </para>
6055
6056 <para>
6057 This change undoes a change made two minor releases ago, instead
6058 throwing an error if a sub-select references a CTE that's below the
6059 semantic level that standard SQL rules would assign to the aggregate
6060 based on contained column references and aggregates. The attempted
6061 fix turned out to cause problems of its own, and it's unclear what
6062 to do instead. Since sub-selects within aggregates are disallowed
6063 altogether by the SQL standard, treating such cases as errors seems
6064 sufficient.
6065 </para>
6066 </listitem>
6067
6068 <listitem>
6069 <!--
6070 Author: Dean Rasheed <[email protected]>
6071 Branch: master [b4307ae2e] 2026-01-24 11:30:48 +0000
6072 Branch: REL_18_STABLE [c6ce4dcf9] 2026-01-24 11:30:48 +0000
6073 Branch: REL_17_STABLE [c5fc17dda] 2026-01-24 11:30:49 +0000
6074 Branch: REL_16_STABLE [e7391bbf1] 2026-01-24 11:30:50 +0000
6075 Branch: REL_15_STABLE [c5824536e] 2026-01-24 11:30:51 +0000
6076 -->
6077 <para>
6078 Fix trigger transition table capture for <command>MERGE</command>
6079 in CTE queries (Dean Rasheed)
6080 <ulink url="&commit_baseurl;c6ce4dcf9">&sect;</ulink>
6081 </para>
6082
6083 <para>
6084 When executing a data-modifying CTE query containing both
6085 a <command>MERGE</command> and another DML operation on a table with
6086 statement-level <literal>AFTER</literal> triggers, the transition
6087 tables passed to the triggers would not include the rows affected by
6088 the <command>MERGE</command>, only those affected by the other
6089 operation(s).
6090 </para>
6091 </listitem>
6092
6093 <listitem>
6094 <!--
6095 Author: Amit Langote <[email protected]>
6096 Branch: master [889676a0d] 2026-01-16 14:53:50 +0900
6097 Branch: REL_18_STABLE [f335457e8] 2026-01-16 14:53:32 +0900
6098 -->
6099 <para>
6100 Fix incorrect pruning of rowmarks belonging to non-relation
6101 rangetable entries, such as subqueries (Dean Rasheed)
6102 <ulink url="&commit_baseurl;f335457e8">&sect;</ulink>
6103 </para>
6104
6105 <para>
6106 This led to incorrect results if a proposed row update needed to be
6107 modified by EvalPlanQual rechecking, as could happen if there was a
6108 concurrent update to that row.
6109 </para>
6110 </listitem>
6111
6112 <listitem>
6113 <!--
6114 Author: Amit Langote <[email protected]>
6115 Branch: master [f9a468c66] 2026-01-23 10:23:30 +0900
6116 Branch: REL_18_STABLE [9f4b7bfc5] 2026-01-23 10:23:26 +0900
6117 Branch: REL_17_STABLE [933f67fb6] 2026-01-23 10:23:22 +0900
6118 Branch: REL_16_STABLE [fab386f74] 2026-01-23 10:23:18 +0900
6119 Branch: REL_15_STABLE [687533b39] 2026-01-23 10:23:14 +0900
6120 Branch: REL_14_STABLE [6d2fa44d2] 2026-01-23 10:23:10 +0900
6121 -->
6122 <para>
6123 Fix failure when all children of a partitioned target table
6124 of an update or delete have been pruned (Amit Langote)
6125 <ulink url="&commit_baseurl;9f4b7bfc5">&sect;</ulink>
6126 </para>
6127
6128 <para>
6129 In such cases, the executor could report <quote>could not find junk
6130 ctid column</quote> errors, even though nothing needs to be done.
6131 </para>
6132 </listitem>
6133
6134 <listitem>
6135 <!--
6136 Author: Andres Freund <[email protected]>
6137 Branch: master [75609fded] 2026-01-06 19:51:10 -0500
6138 Branch: REL_18_STABLE [bdc5dedfc] 2026-01-06 19:51:19 -0500
6139 -->
6140 <para>
6141 Fix expression evaluation bug for a sub-select within an array
6142 subscript (Andres Freund)
6143 <ulink url="&commit_baseurl;bdc5dedfc">&sect;</ulink>
6144 </para>
6145 </listitem>
6146
6147 <listitem>
6148 <!--
6149 Author: Tom Lane <[email protected]>
6150 Branch: master [6dfce8420] 2025-12-05 20:10:33 -0500
6151 Branch: REL_18_STABLE [18b349315] 2025-12-05 20:10:33 -0500
6152 -->
6153 <para>
6154 Fix text substring search for non-deterministic collations
6155 (Laurenz Albe)
6156 <ulink url="&commit_baseurl;18b349315">&sect;</ulink>
6157 </para>
6158
6159 <para>
6160 When using a non-deterministic collation, we failed to detect a
6161 match occurring at the very end of the searched string.
6162 </para>
6163 </listitem>
6164
6165 <listitem>
6166 <!--
6167 Author: David Rowley <[email protected]>
6168 Branch: master [7027dd499] 2026-01-26 23:27:15 +1300
6169 Branch: REL_18_STABLE [ccde5be68] 2026-01-26 23:46:23 +1300
6170 Branch: REL_17_STABLE [cae812741] 2026-01-26 23:47:07 +1300
6171 Branch: REL_16_STABLE [4297a3519] 2026-01-26 23:47:37 +1300
6172 -->
6173 <para>
6174 Avoid possible planner failure when a query contains duplicate
6175 window function calls (Meng Zhang, David Rowley)
6176 <ulink url="&commit_baseurl;ccde5be68">&sect;</ulink>
6177 </para>
6178
6179 <para>
6180 Confusion over de-duplication of such calls could result in errors
6181 like <quote>WindowFunc with winref 2 assigned to WindowAgg with
6182 winref 1</quote>.
6183 </para>
6184 </listitem>
6185
6186 <listitem>
6187 <!--
6188 Author: Richard Guo <[email protected]>
6189 Branch: master [325808cac] 2025-12-25 12:12:52 +0900
6190 Branch: REL_18_STABLE [382ce9cb7] 2025-12-25 12:15:09 +0900
6191 -->
6192 <para>
6193 Fix planner error with set-returning functions and grouping sets
6194 (Richard Guo)
6195 <ulink url="&commit_baseurl;382ce9cb7">&sect;</ulink>
6196 </para>
6197
6198 <para>
6199 When constructing a ProjectSet plan node, the planner failed to
6200 detect that subexpressions involving grouping expressions were
6201 already computed by the input plan. This led to inefficient plans
6202 or errors such as <quote>variable not found in subplan target
6203 list</quote>.
6204 </para>
6205 </listitem>
6206
6207 <listitem>
6208 <!--
6209 Author: Richard Guo <[email protected]>
6210 Branch: master [34740b90b] 2026-01-19 11:13:23 +0900
6211 Branch: REL_18_STABLE [7650eabb6] 2026-01-19 11:14:51 +0900
6212 -->
6213 <para>
6214 Avoid incorrect optimization when a subquery's grouping clause
6215 contains a volatile or set-returning function (Richard Guo)
6216 <ulink url="&commit_baseurl;7650eabb6">&sect;</ulink>
6217 </para>
6218
6219 <para>
6220 The planner was willing to push down outer-query restrictions
6221 referencing such a grouping column, leading to incorrect behavior
6222 due to multiple evaluation of a volatile function, or errors caused
6223 by introduction of a set-returning function into the
6224 subquery's <literal>WHERE</literal>/<literal>HAVING</literal>
6225 clauses.
6226 </para>
6227 </listitem>
6228
6229 <listitem>
6230 <!--
6231 Author: Richard Guo <[email protected]>
6232 Branch: master [559f9e90d] 2025-12-29 11:40:45 +0900
6233 Branch: REL_18_STABLE [7e9f852a7] 2025-12-29 11:44:14 +0900
6234 -->
6235 <para>
6236 Look through PlaceHolderVar nodes when searching for statistics
6237 about an expression (Richard Guo)
6238 <ulink url="&commit_baseurl;7e9f852a7">&sect;</ulink>
6239 </para>
6240
6241 <para>
6242 This change allows the planner to find relevant statistics about
6243 expressions pulled up from subqueries or used in <literal>GROUP
6244 BY</literal>, avoiding falling back to a default estimate.
6245 (Arguably we should adjust any found statistics to account for an
6246 increased probability of the value being NULL, but we've never done
6247 the equivalent thing for plain Vars either.) While this restriction
6248 is old, changes in <productname>PostgreSQL</productname> version 18
6249 made PlaceHolderVars more common than before, so make the change to
6250 avoid plan regressions in affected cases.
6251 </para>
6252 </listitem>
6253
6254 <listitem>
6255 <!--
6256 Author: Richard Guo <[email protected]>
6257 Branch: master [ad66f705f] 2025-12-29 11:38:49 +0900
6258 Branch: REL_18_STABLE [b4cf74420] 2025-12-29 11:43:06 +0900
6259 -->
6260 <para>
6261 Look through no-op PlaceHolderVar nodes when matching expressions to
6262 indexes (Richard Guo)
6263 <ulink url="&commit_baseurl;b4cf74420">&sect;</ulink>
6264 </para>
6265
6266 <para>
6267 Because <productname>PostgreSQL</productname> version 18 uses
6268 PlaceHolderVars in more cases than before, some queries that
6269 formerly could use an index failed to do so. Add logic to prevent
6270 that regression.
6271 </para>
6272 </listitem>
6273
6274 <listitem>
6275 <!--
6276 Author: Tom Lane <[email protected]>
6277 Branch: master [ed931377a] 2025-11-17 13:54:52 -0500
6278 Branch: REL_18_STABLE [bf5b13a8a] 2025-11-17 13:55:26 -0500
6279 -->
6280 <para>
6281 Fix planner's conversion of <literal>OR</literal> clauses to
6282 ScalarArrayOp index conditions (Tender Wang, Tom Lane)
6283 <ulink url="&commit_baseurl;bf5b13a8a">&sect;</ulink>
6284 </para>
6285
6286 <para>
6287 The code did not handle RelabelType nodes correctly, and could
6288 generate invalid expressions or fail to perform a valid conversion.
6289 </para>
6290 </listitem>
6291
6292 <listitem>
6293 <!--
6294 Author: Tom Lane <[email protected]>
6295 Branch: master [5528e8d10] 2025-11-27 13:09:59 -0500
6296 Branch: REL_18_STABLE [a212877dc] 2025-11-27 13:09:59 -0500
6297 Branch: REL_17_STABLE [e79b27662] 2025-11-27 13:09:59 -0500
6298 Branch: REL_16_STABLE [b497766a8] 2025-11-27 13:09:59 -0500
6299 Branch: REL_15_STABLE [f19502f04] 2025-11-27 13:09:59 -0500
6300 Branch: REL_14_STABLE [9e77323fc] 2025-11-27 13:09:59 -0500
6301 -->
6302 <para>
6303 Allow indexscans on partial hash indexes even when the index's
6304 predicate implies the truth of the WHERE clause (Tom Lane)
6305 <ulink url="&commit_baseurl;a212877dc">&sect;</ulink>
6306 </para>
6307
6308 <para>
6309 Normally we drop a WHERE clause that is implied by the predicate,
6310 since it's pointless to test it; it must hold for every index
6311 entry. However that can prevent creation of an indexscan plan if
6312 the index is one that requires a WHERE clause on the leading index
6313 key, as hash indexes do. Don't drop implied clauses when
6314 considering such an index.
6315 </para>
6316 </listitem>
6317
6318 <listitem>
6319 <!--
6320 Author: Heikki Linnakangas <[email protected]>
6321 Branch: master [951b60f7a] 2025-12-18 15:08:48 +0200
6322 Branch: REL_18_STABLE [d77a5f981] 2025-12-18 15:09:26 +0200
6323 Branch: REL_17_STABLE [4b6d096a0] 2025-12-18 15:09:23 +0200
6324 Branch: REL_16_STABLE [a5277700e] 2025-12-18 15:09:21 +0200
6325 Branch: REL_15_STABLE [460d97020] 2025-12-18 15:09:19 +0200
6326 Branch: REL_14_STABLE [ab4256869] 2025-12-18 15:09:17 +0200
6327 -->
6328 <para>
6329 Do not emit WAL for unlogged BRIN indexes (Kirill Reshke)
6330 <ulink url="&commit_baseurl;d77a5f981">&sect;</ulink>
6331 </para>
6332
6333 <para>
6334 One seldom-taken code path incorrectly emitted a WAL record
6335 relating to a BRIN index even if the index was marked unlogged.
6336 Crash recovery would then fail to replay that record, complaining
6337 that the file already exists.
6338 </para>
6339 </listitem>
6340
6341 <listitem>
6342 <!--
6343 Author: Tomas Vondra <[email protected]>
6344 Branch: master [db14dcdec] 2026-01-26 20:05:17 +0100
6345 Branch: REL_18_STABLE [eee71a66c] 2026-01-26 20:05:00 +0100
6346 -->
6347 <para>
6348 Use the correct ordering function in parallel GIN index builds
6349 (Tomas Vondra)
6350 <ulink url="&commit_baseurl;eee71a66c">&sect;</ulink>
6351 </para>
6352
6353 <para>
6354 The parallel code used the default ordering operator (which is
6355 determined by the column data type's btree opclass), whereas it
6356 should use the ordering function specified by the GIN opclass, if
6357 any. This led to a failure if the data type has no btree opclass,
6358 or to an invalid index if the opclass specifies an ordering function
6359 that doesn't agree with the btree opclass.
6360 </para>
6361 </listitem>
6362
6363 <listitem>
6364 <!--
6365 Author: Heikki Linnakangas <[email protected]>
6366 Branch: master [8eeb4a0f7] 2025-11-12 20:59:36 +0200
6367 Branch: REL_18_STABLE [321ec5462] 2025-11-12 21:00:42 +0200
6368 Branch: REL_17_STABLE [d02c03ddc] 2025-11-12 21:01:13 +0200
6369 Branch: REL_16_STABLE [053e1868b] 2025-11-12 21:01:42 +0200
6370 Branch: REL_15_STABLE [1a469d7b5] 2025-11-12 21:02:12 +0200
6371 Branch: REL_14_STABLE [eba917d36] 2025-11-12 21:02:36 +0200
6372 Branch: master [797e9ea6e] 2025-11-12 20:59:44 +0200
6373 Branch: REL_18_STABLE [7b069a187] 2025-11-12 21:00:46 +0200
6374 Branch: REL_17_STABLE [c2682810a] 2025-11-12 21:01:16 +0200
6375 Branch: REL_16_STABLE [44e8c60be] 2025-11-12 21:01:45 +0200
6376 Branch: REL_15_STABLE [0c862646c] 2025-11-12 21:02:14 +0200
6377 Branch: REL_14_STABLE [c2e58c071] 2025-11-12 21:02:38 +0200
6378 Branch: master [0bdc777e8] 2025-11-12 21:19:03 +0200
6379 Branch: REL_18_STABLE [82fa6b78d] 2025-11-12 21:26:58 +0200
6380 Branch: REL_17_STABLE [d80d5f099] 2025-11-12 21:27:02 +0200
6381 Branch: REL_16_STABLE [0e8eaa218] 2025-11-12 21:27:05 +0200
6382 Branch: REL_15_STABLE [21a9014cf] 2025-11-12 21:27:07 +0200
6383 Branch: REL_14_STABLE [84f1bf4af] 2025-11-12 21:27:11 +0200
6384 -->
6385 <para>
6386 Prevent truncation of CLOG that is still needed by
6387 unread <command>NOTIFY</command> messages (Joel Jacobson, Heikki
6388 Linnakangas)
6389 <ulink url="&commit_baseurl;321ec5462">&sect;</ulink>
6390 <ulink url="&commit_baseurl;7b069a187">&sect;</ulink>
6391 <ulink url="&commit_baseurl;82fa6b78d">&sect;</ulink>
6392 </para>
6393
6394 <para>
6395 This fix prevents <quote>could not access status of
6396 transaction</quote> errors when a backend is slow to
6397 absorb <command>NOTIFY</command> messages.
6398 </para>
6399 </listitem>
6400
6401 <listitem>
6402 <!--
6403 Author: Heikki Linnakangas <[email protected]>
6404 Branch: master [1b4699090] 2025-11-12 20:59:28 +0200
6405 Branch: REL_18_STABLE [aab4a84bb] 2025-11-12 21:00:25 +0200
6406 Branch: REL_17_STABLE [b821c9292] 2025-11-12 21:01:08 +0200
6407 Branch: REL_16_STABLE [c1a5bde00] 2025-11-12 21:01:39 +0200
6408 Branch: REL_15_STABLE [b1da37de2] 2025-11-12 21:02:07 +0200
6409 Branch: REL_14_STABLE [7cb05dd2d] 2025-11-12 21:02:32 +0200
6410 -->
6411 <para>
6412 Escalate errors occurring during <command>NOTIFY</command> message
6413 processing to FATAL, i.e. close the connection (Heikki Linnakangas)
6414 <ulink url="&commit_baseurl;aab4a84bb">&sect;</ulink>
6415 </para>
6416
6417 <para>
6418 Formerly, if a backend got an error while absorbing
6419 a <command>NOTIFY</command> message, it would advance past that
6420 message, report the error to the client, and move on. That behavior
6421 was fraught with problems though. One big concern is that the
6422 client has no good way to know that a notification was lost, and
6423 certainly no way to know what was in it. Depending on the
6424 application logic, missing a notification could cause the
6425 application to get stuck waiting, for example. Also, any remaining
6426 messages would not get processed until someone sent a
6427 new <command>NOTIFY</command>.
6428 </para>
6429
6430 <para>
6431 Also, if the connection is idle at the time of receiving
6432 a <command>NOTIFY</command> signal, any ERROR would be escalated to
6433 FATAL anyway, due to unrelated concerns. Therefore, we've chosen to
6434 make that happen in all cases, for consistency and to provide a
6435 clear signal to the application that it might have missed some
6436 notifications.
6437 </para>
6438 </listitem>
6439
6440 <listitem>
6441 <!--
6442 Author: Michael Paquier <[email protected]>
6443 Branch: master [e217dc748] 2026-01-14 08:44:12 +0900
6444 Branch: REL_18_STABLE [9c3caad02] 2026-01-14 08:44:52 +0900
6445 -->
6446 <para>
6447 Consider grouping expressions when computing a query ID hash
6448 (Jian He)
6449 <ulink url="&commit_baseurl;9c3caad02">&sect;</ulink>
6450 </para>
6451
6452 <para>
6453 Previously, two queries that were the same except in <literal>GROUP
6454 BY</literal> expressions would be merged
6455 by <filename>contrib/pg_stat_statements</filename> and other users
6456 of query IDs.
6457 </para>
6458 </listitem>
6459
6460 <listitem>
6461 <!--
6462 Author: Dean Rasheed <[email protected]>
6463 Branch: master [1b92fe7bb] 2025-11-16 22:14:06 +0000
6464 Branch: REL_18_STABLE [5749d95d4] 2025-11-16 22:15:10 +0000
6465 Branch: REL_17_STABLE [d6c415c4b] 2025-11-16 22:15:45 +0000
6466 -->
6467 <para>
6468 Fix erroneous counting of updates in <command>EXPLAIN ANALYZE
6469 MERGE</command> with a concurrent update (Dean Rasheed)
6470 <ulink url="&commit_baseurl;5749d95d4">&sect;</ulink>
6471 </para>
6472
6473 <para>
6474 This situation led to an incorrect count of <quote>skipped</quote>
6475 tuples in <command>EXPLAIN</command>'s output, or to an assertion
6476 failure in an assert-enabled build.
6477 </para>
6478 </listitem>
6479
6480 <listitem>
6481 <!--
6482 Author: Heikki Linnakangas <[email protected]>
6483 Branch: master [955f55068] 2025-12-23 13:37:16 +0200
6484 Branch: REL_18_STABLE [3e3a80f62] 2025-12-23 13:37:23 +0200
6485 Branch: REL_17_STABLE [bb87d7fef] 2025-12-23 13:37:25 +0200
6486 Branch: REL_16_STABLE [7efef18ff] 2025-12-23 13:37:27 +0200
6487 Branch: REL_15_STABLE [5d5487cd2] 2025-12-23 13:37:29 +0200
6488 Branch: REL_14_STABLE [b6201c76e] 2025-12-23 13:37:31 +0200
6489 -->
6490 <para>
6491 Fix bug in following update chain when locking a tuple (Jasper
6492 Smit)
6493 <ulink url="&commit_baseurl;3e3a80f62">&sect;</ulink>
6494 </para>
6495
6496 <para>
6497 This code path neglected to check the xmin of the first new tuple in
6498 the update chain, making it possible to lock an unrelated tuple if
6499 the original updater aborted and the space was immediately reclaimed
6500 by <command>VACUUM</command> and then re-used.
6501 That could cause unexpected transaction delays or deadlocks.
6502 Errors associated with having identified the wrong tuple have also
6503 been observed.
6504 </para>
6505 </listitem>
6506
6507 <listitem>
6508 <!--
6509 Author: Robert Haas <[email protected]>
6510 Branch: master [ecd275718] 2026-01-19 12:09:32 -0500
6511 Branch: REL_18_STABLE [c80b0c9d6] 2026-01-19 12:09:48 -0500
6512 Branch: REL_17_STABLE [ad569b54a] 2026-01-19 12:10:00 -0500
6513 -->
6514 <para>
6515 Fix incorrect handling of incremental backups of large tables
6516 (Robert Haas, Oleg Tkachenko)
6517 <ulink url="&commit_baseurl;c80b0c9d6">&sect;</ulink>
6518 </para>
6519
6520 <para>
6521 If a table exceeding 1GB (or in general, the installation's segment
6522 size) is truncated by <literal>VACUUM</literal> between the base
6523 backup and the incremental
6524 backup, <application>pg_combinebackup</application> could fail with
6525 an error about <quote>truncation block length in excess of segment
6526 size</quote>. This prevented restoring the incremental backup.
6527 </para>
6528 </listitem>
6529
6530 <listitem>
6531 <!--
6532 Author: Amit Langote <[email protected]>
6533 Branch: master [9cbb1d21d] 2026-01-16 13:02:42 +0900
6534 Branch: REL_18_STABLE [1943ceb38] 2026-01-16 13:14:21 +0900
6535 Branch: REL_17_STABLE [4071fe900] 2026-01-16 13:19:53 +0900
6536 Branch: REL_16_STABLE [980b7c736] 2026-01-16 13:19:59 +0900
6537 Branch: REL_15_STABLE [b926ff137] 2026-01-16 13:20:05 +0900
6538 Branch: REL_14_STABLE [f6df78173] 2026-01-16 13:20:11 +0900
6539 -->
6540 <para>
6541 Fix potential backend process crash at process exit due to trying to
6542 release a lock in an already-unmapped shared memory segment
6543 (Rahila Syed)
6544 <ulink url="&commit_baseurl;1943ceb38">&sect;</ulink>
6545 </para>
6546 </listitem>
6547
6548 <listitem>
6549 <!--
6550 Author: Andres Freund <[email protected]>
6551 Branch: master [807764990] 2026-01-15 11:09:07 -0500
6552 Branch: REL_18_STABLE [7f1b3a4ce] 2026-01-15 11:09:49 -0500
6553 -->
6554 <para>
6555 Fix race condition in async I/O code (Andres Freund)
6556 <ulink url="&commit_baseurl;7f1b3a4ce">&sect;</ulink>
6557 </para>
6558
6559 <para>
6560 It was possible for the result code of an asynchronous I/O operation
6561 to be overwritten before it was fetched.
6562 </para>
6563 </listitem>
6564
6565 <listitem>
6566 <!--
6567 Author: Heikki Linnakangas <[email protected]>
6568 Branch: master [102bdaa9b] 2026-01-15 16:48:45 +0200
6569 Branch: REL_18_STABLE [09532a78b] 2026-01-15 16:49:42 +0200
6570 Branch: REL_17_STABLE [d3ad4cef6] 2026-01-15 16:50:30 +0200
6571 Branch: REL_16_STABLE [c7946e6f3] 2026-01-15 16:50:37 +0200
6572 Branch: REL_15_STABLE [a563ac619] 2026-01-15 16:50:42 +0200
6573 Branch: REL_14_STABLE [46be454ca] 2026-01-15 16:50:46 +0200
6574 -->
6575 <para>
6576 Guard against incorrect truncation of the multixact log after a
6577 crash (Heikki Linnakangas)
6578 <ulink url="&commit_baseurl;09532a78b">&sect;</ulink>
6579 </para>
6580 </listitem>
6581
6582 <listitem>
6583 <!--
6584 Author: Michael Paquier <[email protected]>
6585 Branch: master [36b8f4974] 2025-12-27 17:23:30 +0900
6586 Branch: REL_18_STABLE [06907e864] 2025-12-27 17:23:51 +0900
6587 Branch: REL_17_STABLE [52b27f585] 2025-12-27 17:23:53 +0900
6588 Branch: REL_16_STABLE [c48829ed8] 2025-12-27 17:23:54 +0900
6589 Branch: REL_15_STABLE [300575fe2] 2025-12-27 17:23:56 +0900
6590 Branch: REL_14_STABLE [ea3524cff] 2025-12-27 17:23:58 +0900
6591 -->
6592 <para>
6593 Fix possibly mis-encoded result
6594 of <function>pg_stat_get_backend_activity()</function> (Chao Li)
6595 <ulink url="&commit_baseurl;06907e864">&sect;</ulink>
6596 </para>
6597
6598 <para>
6599 The shared-memory buffer holding a session's activity string can
6600 end with an incomplete multibyte character. Readers are supposed
6601 to truncate off any such incomplete character, but this function
6602 failed to do so.
6603 </para>
6604 </listitem>
6605
6606 <listitem>
6607 <!--
6608 Author: Fujii Masao <[email protected]>
6609 Branch: master [b3ccb0a2c] 2025-12-19 12:05:37 +0900
6610 Branch: REL_18_STABLE [b863d8d87] 2025-12-19 12:07:10 +0900
6611 Branch: REL_17_STABLE [699293d27] 2025-12-19 12:07:21 +0900
6612 Branch: REL_16_STABLE [3853f6168] 2025-12-19 12:08:20 +0900
6613 Branch: REL_15_STABLE [0fc2f533a] 2025-12-19 12:09:10 +0900
6614 Branch: REL_14_STABLE [1a9a49699] 2025-12-19 12:09:16 +0900
6615 -->
6616 <para>
6617 Guard against recursive memory context logging (Fujii Masao)
6618 <ulink url="&commit_baseurl;b863d8d87">&sect;</ulink>
6619 </para>
6620
6621 <para>
6622 A constant flow of signals requesting memory context logging could
6623 cause recursive execution of the logging code, which in theory could
6624 lead to stack overflow.
6625 </para>
6626 </listitem>
6627
6628 <listitem>
6629 <!--
6630 Author: Robert Haas <[email protected]>
6631 Branch: master [f1a6e622b] 2025-12-16 12:24:55 -0500
6632 Branch: REL_18_STABLE [57df5ab80] 2025-12-16 10:59:05 -0500
6633 Branch: REL_17_STABLE [1d0fc2499] 2025-12-16 10:59:04 -0500
6634 Branch: REL_16_STABLE [12c2f843c] 2025-12-16 10:59:02 -0500
6635 Branch: REL_15_STABLE [bd2726d3e] 2025-12-16 10:59:01 -0500
6636 Branch: REL_14_STABLE [1d9f7fbba] 2025-12-16 10:59:00 -0500
6637 -->
6638 <para>
6639 Fix memory context usage when reinitializing a parallel execution
6640 context (Jakub Wartak, Jeevan Chalke)
6641 <ulink url="&commit_baseurl;57df5ab80">&sect;</ulink>
6642 </para>
6643
6644 <para>
6645 This error could result in a crash due to a subsidiary data
6646 structure having a shorter lifespan than the parallel context.
6647 The problem is not known to be reachable using only
6648 core <productname>PostgreSQL</productname>, but we have reports of
6649 trouble in extensions.
6650 </para>
6651 </listitem>
6652
6653 <listitem>
6654 <!--
6655 Author: Heikki Linnakangas <[email protected]>
6656 Branch: master [789d65364] 2025-12-03 19:15:08 +0200
6657 Branch: REL_18_STABLE [e46041fd9] 2025-12-03 19:15:18 +0200
6658 Branch: REL_17_STABLE [8ba61bc06] 2025-12-03 19:15:21 +0200
6659 Branch: REL_16_STABLE [635166913] 2025-12-03 19:15:24 +0200
6660 Branch: REL_15_STABLE [8cfb174a6] 2025-12-03 19:15:26 +0200
6661 Branch: REL_14_STABLE [81416e101] 2025-12-03 19:15:29 +0200
6662 Branch: master [4d936c3ff] 2025-12-05 11:32:38 +0200
6663 Branch: REL_18_STABLE [02ba5e3be] 2025-12-05 11:35:20 +0200
6664 Branch: REL_17_STABLE [cad40cec2] 2025-12-05 11:35:44 +0200
6665 Branch: REL_16_STABLE [4d689a176] 2025-12-05 11:36:36 +0200
6666 Branch: REL_15_STABLE [b9a02b978] 2025-12-05 11:36:52 +0200
6667 Branch: REL_14_STABLE [489695554] 2025-12-05 11:37:06 +0200
6668 -->
6669 <para>
6670 Set next multixid's offset when creating a new multixid, to remove
6671 the wait loop that was needed in corner cases (Andrey Borodin)
6672 <ulink url="&commit_baseurl;e46041fd9">&sect;</ulink>
6673 <ulink url="&commit_baseurl;02ba5e3be">&sect;</ulink>
6674 </para>
6675
6676 <para>
6677 The previous logic could get stuck waiting for an update that would
6678 never occur.
6679 </para>
6680 </listitem>
6681
6682 <listitem>
6683 <!--
6684 Author: Dean Rasheed <[email protected]>
6685 Branch: master [3881561d7] 2025-11-29 12:28:59 +0000
6686 Branch: REL_18_STABLE [b880d9a02] 2025-11-29 12:31:30 +0000
6687 Branch: REL_17_STABLE [c09096503] 2025-11-29 12:32:12 +0000
6688 Branch: REL_16_STABLE [4d288e33b] 2025-11-29 12:33:04 +0000
6689 Branch: REL_15_STABLE [134a8ee22] 2025-11-29 12:33:35 +0000
6690 Branch: REL_14_STABLE [2d5b97b8c] 2025-11-29 12:34:45 +0000
6691 -->
6692 <para>
6693 Avoid rewriting data-modifying CTEs more than once (Bernice Southey,
6694 Dean Rasheed)
6695 <ulink url="&commit_baseurl;b880d9a02">&sect;</ulink>
6696 </para>
6697
6698 <para>
6699 Formerly, when updating an auto-updatable view or a relation with
6700 rules, if the original query had any data-modifying CTEs, the rewriter
6701 would rewrite those CTEs multiple times due to recursion. This was
6702 inefficient and could produce false errors if a CTE included an
6703 update of an always-generated column.
6704 </para>
6705 </listitem>
6706
6707 <listitem>
6708 <!--
6709 Author: Nathan Bossart <[email protected]>
6710 Branch: master [dbdc717ac] 2025-11-26 15:12:25 -0600
6711 Branch: REL_18_STABLE [b83bcc0df] 2025-11-26 15:12:25 -0600
6712 Branch: REL_17_STABLE [2fc5c5062] 2025-11-26 15:12:25 -0600
6713 -->
6714 <para>
6715 Allow retrying initialization of a DSM registry entry
6716 (Nathan Bossart)
6717 <ulink url="&commit_baseurl;b83bcc0df">&sect;</ulink>
6718 </para>
6719
6720 <para>
6721 If we fail partway through initialization of a dynamic shared memory
6722 entry, allow the next attempt to use that entry to retry
6723 initialization. Previously the entry was left in a
6724 permanently-failed state.
6725 </para>
6726 </listitem>
6727
6728 <listitem>
6729 <!--
6730 Author: Tomas Vondra <[email protected]>
6731 Branch: master [3fccbd94c] 2026-01-27 00:21:40 +0100
6732 Branch: REL_18_STABLE [9796c4f56] 2026-01-26 23:37:03 +0100
6733 -->
6734 <para>
6735 Avoid failure of NUMA status views when a page has been swapped out
6736 (Tomas Vondra)
6737 <ulink url="&commit_baseurl;9796c4f56">&sect;</ulink>
6738 </para>
6739 </listitem>
6740
6741 <listitem>
6742 <!--
6743 Author: Tomas Vondra <[email protected]>
6744 Branch: master [599336c64] 2025-11-20 13:26:49 +0100
6745 Branch: REL_18_STABLE [482e98ac4] 2025-11-20 13:26:14 +0100
6746 -->
6747 <para>
6748 Avoid <quote>operation not permitted</quote> errors when querying
6749 NUMA page status with older libnuma versions (Tomas Vondra)
6750 <ulink url="&commit_baseurl;482e98ac4">&sect;</ulink>
6751 </para>
6752 </listitem>
6753
6754 <listitem>
6755 <!--
6756 Author: Michael Paquier <[email protected]>
6757 Branch: master [dc7c77f82] 2025-12-16 13:29:28 +0900
6758 Branch: REL_18_STABLE [68ebdf2b0] 2025-12-16 13:29:36 +0900
6759 Branch: REL_17_STABLE [f5927da4f] 2025-12-16 13:29:39 +0900
6760 Branch: REL_16_STABLE [1aa57e9ed] 2025-12-16 13:29:41 +0900
6761 Branch: REL_15_STABLE [95ef6f490] 2025-12-16 13:29:42 +0900
6762 Branch: REL_14_STABLE [14161bca4] 2025-12-16 13:29:44 +0900
6763 -->
6764 <para>
6765 Fail recovery if WAL does not exist back to the redo point indicated
6766 by the checkpoint record (Nitin Jadhav)
6767 <ulink url="&commit_baseurl;68ebdf2b0">&sect;</ulink>
6768 </para>
6769
6770 <para>
6771 Add an explicit check for this before starting recovery, so that no
6772 harm is done and a useful error message is provided. Previously,
6773 recovery might crash or corrupt the database in this situation.
6774 </para>
6775 </listitem>
6776
6777 <listitem>
6778 <!--
6779 Author: David Rowley <[email protected]>
6780 Branch: master [6ca8506ea] 2026-01-06 17:29:12 +1300
6781 Branch: REL_18_STABLE [bea57a6b4] 2026-01-06 17:29:44 +1300
6782 Branch: REL_17_STABLE [bb08ac7ac] 2026-01-06 17:30:08 +1300
6783 Branch: REL_16_STABLE [0687a6eb0] 2026-01-06 17:30:32 +1300
6784 Branch: REL_15_STABLE [f20b79059] 2026-01-06 17:30:57 +1300
6785 Branch: REL_14_STABLE [ae45c7296] 2026-01-06 17:31:20 +1300
6786 -->
6787 <para>
6788 Avoid scribbling on the source query tree during <command>ALTER
6789 PUBLICATION</command> (Sunil S)
6790 <ulink url="&commit_baseurl;bea57a6b4">&sect;</ulink>
6791 </para>
6792
6793 <para>
6794 This error had the visible effect that an event trigger fired for
6795 the query would see only the first <literal>publish</literal>
6796 option, even if several had been specified. If such a query were
6797 set up as a prepared statement, re-executions would misbehave too.
6798 </para>
6799 </listitem>
6800
6801 <listitem>
6802 <!--
6803 Author: Fujii Masao <[email protected]>
6804 Branch: master [d926462d8] 2026-01-06 11:52:22 +0900
6805 Branch: REL_18_STABLE [797fc5d1b] 2026-01-06 11:54:09 +0900
6806 Branch: REL_17_STABLE [7a990e801] 2026-01-06 11:54:14 +0900
6807 Branch: REL_16_STABLE [75f3428f2] 2026-01-06 11:54:46 +0900
6808 Branch: REL_15_STABLE [f7eb44e0f] 2026-01-06 11:55:46 +0900
6809 -->
6810 <para>
6811 Pass connection options specified in <literal>CREATE SUBSCRIPTION
6812 ... CONNECTION</literal> to the publisher's walsender (Fujii Masao)
6813 <ulink url="&commit_baseurl;797fc5d1b">&sect;</ulink>
6814 </para>
6815
6816 <para>
6817 Before this fix, the <literal>options</literal> connection option
6818 (if any) was ignored, thus for example preventing setting custom
6819 server parameter values in the walsender session. It was intended
6820 for that to work, and it did work before refactoring
6821 in <productname>PostgreSQL</productname> version 15 broke it, so
6822 restore the previous behavior.
6823 </para>
6824 </listitem>
6825
6826 <listitem>
6827 <!--
6828 Author: Amit Kapila <[email protected]>
6829 Branch: master [851f6649c] 2026-01-27 05:06:29 +0000
6830 Branch: REL_18_STABLE [919c9fa13] 2026-01-27 05:45:25 +0000
6831 Branch: REL_17_STABLE [3243c0177] 2026-01-27 05:49:23 +0000
6832 Branch: master [3a98f989e] 2026-01-29 03:22:02 +0000
6833 Branch: REL_18_STABLE [1c60f7236] 2026-01-29 03:34:55 +0000
6834 Branch: REL_17_STABLE [9649f1adf] 2026-01-29 02:57:02 +0000
6835 Branch: master [006dd4b2e] 2025-12-08 05:21:22 +0000
6836 Branch: REL_18_STABLE [d3ceb2084] 2025-12-08 05:33:14 +0000
6837 Branch: REL_17_STABLE [3510ebeb0] 2026-01-08 07:17:56 +0000
6838 Branch: REL_16_STABLE [24cce33c3] 2026-01-08 07:07:23 +0000
6839 Branch: REL_15_STABLE [aae05622a] 2026-01-08 06:54:52 +0000
6840 Branch: REL_14_STABLE [7406df605] 2026-01-08 06:44:28 +0000
6841 -->
6842 <para>
6843 Prevent invalidation of newly created or newly synced replication
6844 slots (Zhijie Hou)
6845 <ulink url="&commit_baseurl;919c9fa13">&sect;</ulink>
6846 <ulink url="&commit_baseurl;1c60f7236">&sect;</ulink>
6847 <ulink url="&commit_baseurl;d3ceb2084">&sect;</ulink>
6848 </para>
6849
6850 <para>
6851 A race condition with a concurrent checkpoint could allow WAL to be
6852 removed that is needed by the replication slot, causing the slot to
6853 immediately get marked invalid.
6854 </para>
6855 </listitem>
6856
6857 <listitem>
6858 <!--
6859 Author: Masahiko Sawada <[email protected]>
6860 Branch: master [2a5225b99] 2025-12-30 10:56:30 -0800
6861 Branch: REL_18_STABLE [fd7c86cfa] 2025-12-30 10:56:28 -0800
6862 Branch: REL_17_STABLE [123b851ab] 2025-12-30 10:56:25 -0800
6863 Branch: REL_16_STABLE [821466722] 2025-12-30 10:56:23 -0800
6864 Branch: REL_15_STABLE [fa557d300] 2025-12-30 10:56:21 -0800
6865 Branch: REL_14_STABLE [57048d6e1] 2025-12-30 10:56:18 -0800
6866 -->
6867 <para>
6868 Fix race condition in computing a replication slot's required xmin
6869 (Zhijie Hou)
6870 <ulink url="&commit_baseurl;fd7c86cfa">&sect;</ulink>
6871 </para>
6872
6873 <para>
6874 This could lead to the error <quote>cannot build an initial slot
6875 snapshot as oldest safe xid follows snapshot's xmin</quote>.
6876 </para>
6877 </listitem>
6878
6879 <listitem>
6880 <!--
6881 Author: Michael Paquier <[email protected]>
6882 Branch: master [8e0d32a4a] 2025-12-23 14:32:14 +0900
6883 Branch: REL_18_STABLE [b07c32619] 2025-12-23 14:32:19 +0900
6884 Branch: REL_17_STABLE [e063ccc72] 2025-12-23 14:32:21 +0900
6885 Branch: REL_16_STABLE [e22e9ab0c] 2025-12-23 14:32:22 +0900
6886 Branch: REL_15_STABLE [90d1beef6] 2025-12-23 14:32:24 +0900
6887 Branch: REL_14_STABLE [25a04aa52] 2025-12-23 14:32:25 +0900
6888 -->
6889 <para>
6890 During initial synchronization of a logical replication
6891 subscription, commit the addition of
6892 a <structname>pg_replication_origin</structname> entry before
6893 starting to copy data (Zhijie Hou)
6894 <ulink url="&commit_baseurl;b07c32619">&sect;</ulink>
6895 </para>
6896
6897 <para>
6898 Previously, if the copy step failed, the
6899 new <structname>pg_replication_origin</structname> entry would be
6900 lost due to transaction rollback. This led to inconsistent state in
6901 shared memory.
6902 </para>
6903 </listitem>
6904
6905 <listitem>
6906 <!--
6907 Author: Amit Kapila <[email protected]>
6908 Branch: master [1528b0d89] 2025-12-24 04:36:39 +0000
6909 Branch: REL_18_STABLE [2f7ffe124] 2025-12-24 04:21:43 +0000
6910 Branch: REL_17_STABLE [0ed8f1afb] 2025-12-24 04:05:06 +0000
6911 Branch: REL_16_STABLE [63a65adf4] 2025-12-24 04:19:57 +0000
6912 -->
6913 <para>
6914 Don't advance logical replication progress after a parallel worker
6915 apply failure (Zhijie Hou)
6916 <ulink url="&commit_baseurl;2f7ffe124">&sect;</ulink>
6917 </para>
6918
6919 <para>
6920 The previous behavior allowed transactions to be lost by a
6921 subscriber.
6922 </para>
6923 </listitem>
6924
6925 <listitem>
6926 <!--
6927 Author: Amit Kapila <[email protected]>
6928 Branch: master [04396eacd] 2025-12-09 07:25:20 +0000
6929 Branch: REL_18_STABLE [6c61c69d5] 2025-12-09 07:12:37 +0000
6930 Branch: REL_17_STABLE [f2818868a] 2025-12-09 07:02:08 +0000
6931 -->
6932 <para>
6933 Fix logical replication slotsync worker processes to handle
6934 LOCK_TIMEOUT signals correctly (Zhijie Hou)
6935 <ulink url="&commit_baseurl;6c61c69d5">&sect;</ulink>
6936 </para>
6937
6938 <para>
6939 Previously, timeout signals were effectively ignored.
6940 </para>
6941 </listitem>
6942
6943 <listitem>
6944 <!--
6945 Author: Heikki Linnakangas <[email protected]>
6946 Branch: master [23b25586d] 2026-01-15 21:02:49 +0200
6947 Branch: REL_18_STABLE [9ed411e08] 2026-01-15 21:02:54 +0200
6948 Branch: REL_17_STABLE [c3770181c] 2026-01-15 21:02:59 +0200
6949 Branch: REL_16_STABLE [a2eeb04f3] 2026-01-15 21:03:12 +0200
6950 Branch: REL_15_STABLE [ef8465588] 2026-01-15 21:03:16 +0200
6951 Branch: REL_14_STABLE [2514f1c77] 2026-01-15 20:58:05 +0200
6952 -->
6953 <para>
6954 Fix possible failure with <quote>unexpected data beyond EOF</quote>
6955 during restart of a streaming replica server (Anthonin Bonnefoy)
6956 <ulink url="&commit_baseurl;9ed411e08">&sect;</ulink>
6957 </para>
6958 </listitem>
6959
6960 <listitem>
6961 <!--
6962 Author: Amit Langote <[email protected]>
6963 Branch: master [519fa0433] 2025-11-27 12:07:01 +0900
6964 Branch: REL_18_STABLE [15ba0702c] 2025-11-27 11:59:40 +0900
6965 Branch: REL_17_STABLE [b5511fed5] 2025-11-27 11:59:36 +0900
6966 -->
6967 <para>
6968 Fix error reporting for SQL/JSON path type mismatches (Jian He)
6969 <ulink url="&commit_baseurl;15ba0702c">&sect;</ulink>
6970 </para>
6971
6972 <para>
6973 The code could produce a <quote>cache lookup failed for type 0</quote>
6974 error instead of the intended complaint about the path expression
6975 not being of the right type.
6976 </para>
6977 </listitem>
6978
6979 <listitem>
6980 <!--
6981 Author: David Rowley <[email protected]>
6982 Branch: master [349107537] 2026-01-09 11:01:36 +1300
6983 Branch: REL_18_STABLE [c35e5dd9a] 2026-01-09 11:02:59 +1300
6984 Branch: REL_17_STABLE [84b787ae6] 2026-01-09 11:03:24 +1300
6985 Branch: REL_16_STABLE [821c4d27b] 2026-01-09 11:03:48 +1300
6986 Branch: REL_15_STABLE [3ad05640b] 2026-01-09 11:04:12 +1300
6987 Branch: REL_14_STABLE [a65995947] 2026-01-09 11:04:39 +1300
6988 -->
6989 <para>
6990 Fix erroneous tracking of column position when parsing partition
6991 range bounds (myzhen)
6992 <ulink url="&commit_baseurl;c35e5dd9a">&sect;</ulink>
6993 </para>
6994
6995 <para>
6996 This could, for example, lead to the wrong column name being cited
6997 in error messages about casting partition bound values to the
6998 column's data type.
6999 </para>
7000 </listitem>
7001
7002 <listitem>
7003 <!--
7004 Author: Michael Paquier <[email protected]>
7005 Branch: master [74a116a79] 2026-02-06 15:38:16 +0900
7006 Branch: REL_18_STABLE [acfa422c3] 2026-02-06 15:38:21 +0900
7007 Branch: REL_17_STABLE [67ad4387b] 2026-02-06 15:38:23 +0900
7008 Branch: REL_16_STABLE [977a17a3e] 2026-02-06 15:38:25 +0900
7009 Branch: REL_15_STABLE [4ec943f7d] 2026-02-06 15:38:27 +0900
7010 Branch: REL_14_STABLE [d32e17160] 2026-02-06 15:38:29 +0900
7011 Branch: master [c8ec74713] 2026-02-04 16:38:06 +0900
7012 Branch: REL_18_STABLE [2ca4464b6] 2026-02-04 16:38:10 +0900
7013 Branch: REL_17_STABLE [263af458e] 2026-02-04 16:38:12 +0900
7014 Branch: master [a9afa021e] 2026-02-02 10:21:04 +0900
7015 Branch: REL_18_STABLE [ab61f0087] 2026-02-02 10:21:07 +0900
7016 Branch: REL_17_STABLE [5995135f1] 2026-02-02 10:21:10 +0900
7017 Branch: master [6bca4b50d] 2026-01-18 17:24:25 +0900
7018 Branch: REL_18_STABLE [69ee81932] 2026-01-18 17:24:58 +0900
7019 Branch: REL_17_STABLE [05ef2371a] 2026-01-18 17:25:00 +0900
7020 Branch: REL_16_STABLE [e8fd6c9fd] 2026-01-18 17:25:01 +0900
7021 Branch: REL_15_STABLE [fbf8df580] 2026-01-18 17:25:03 +0900
7022 Branch: REL_14_STABLE [f1dc7a5b7] 2026-01-18 17:25:04 +0900
7023 Author: Peter Eisentraut <[email protected]>
7024 Branch: master [1653ce523] 2026-02-07 22:37:02 +0100
7025 Branch: REL_18_STABLE [cff2ef984] 2026-02-07 22:53:16 +0100
7026 Branch: REL_17_STABLE [5449fd261] 2026-02-07 22:53:21 +0100
7027 Branch: REL_16_STABLE [a7bdbbada] 2026-02-07 22:53:25 +0100
7028 Branch: REL_15_STABLE [9dcd0b3de] 2026-02-07 22:53:34 +0100
7029 Branch: REL_14_STABLE [3e7bb39df] 2026-02-07 22:53:38 +0100
7030 -->
7031 <para>
7032 Fix assorted minor errors in error messages (Man Zeng, Tianchen Zhang)
7033 <ulink url="&commit_baseurl;acfa422c3">&sect;</ulink>
7034 <ulink url="&commit_baseurl;2ca4464b6">&sect;</ulink>
7035 <ulink url="&commit_baseurl;ab61f0087">&sect;</ulink>
7036 <ulink url="&commit_baseurl;69ee81932">&sect;</ulink>
7037 <ulink url="&commit_baseurl;cff2ef984">&sect;</ulink>
7038 </para>
7039
7040 <para>
7041 For example, an error report about mismatched timeline number in a
7042 backup manifest showed the starting timeline number where it meant
7043 to show the ending timeline number.
7044 </para>
7045 </listitem>
7046
7047 <listitem>
7048 <!--
7049 Author: Thomas Munro <[email protected]>
7050 Branch: master [e5d99b4d9] 2026-01-22 16:03:47 +1300
7051 Branch: REL_18_STABLE [f1c6b153c] 2026-01-22 16:10:58 +1300
7052 Branch: REL_17_STABLE [d0bb0e5b3] 2026-01-22 16:10:28 +1300
7053 Branch: REL_16_STABLE [7600dc79c] 2026-01-22 16:10:08 +1300
7054 Branch: REL_15_STABLE [cbdd09ae1] 2026-01-22 16:09:29 +1300
7055 Branch: REL_14_STABLE [de8081c30] 2026-01-22 16:06:06 +1300
7056 -->
7057 <para>
7058 Fix failure to perform function inlining when doing JIT compilation
7059 with LLVM version 17 or later (Anthonin Bonnefoy)
7060 <ulink url="&commit_baseurl;f1c6b153c">&sect;</ulink>
7061 </para>
7062 </listitem>
7063
7064 <listitem>
7065 <!--
7066 Author: Thomas Munro <[email protected]>
7067 Branch: master [0dceba21d] 2025-11-22 21:21:11 +1300
7068 Branch: REL_18_STABLE [912cfa314] 2025-11-22 21:21:54 +1300
7069 Branch: REL_17_STABLE [60215eae7] 2025-11-22 21:22:37 +1300
7070 Branch: REL_16_STABLE [600acd34b] 2025-11-22 21:23:23 +1300
7071 Branch: REL_15_STABLE [55164852d] 2025-11-22 21:23:45 +1300
7072 Branch: REL_14_STABLE [035a1f5ac] 2025-11-22 21:20:27 +1300
7073 -->
7074 <para>
7075 Adjust our JIT code to work with LLVM 21 (Holger Hoffstätte)
7076 <ulink url="&commit_baseurl;912cfa314">&sect;</ulink>
7077 </para>
7078
7079 <para>
7080 The previous coding failed to compile on aarch64 machines.
7081 </para>
7082 </listitem>
7083
7084 <listitem>
7085 <!--
7086 Author: Tom Lane <[email protected]>
7087 Branch: master [6d969ca68] 2025-11-17 15:24:34 -0500
7088 Branch: REL_18_STABLE [db4eba152] 2025-11-17 15:24:40 -0500
7089 Branch: master [3e83bdd35] 2025-11-18 16:16:46 -0500
7090 Branch: REL_18_STABLE [6a5170755] 2025-11-18 16:16:51 -0500
7091 -->
7092 <para>
7093 Fix aarch64-specific code to build with old (RHEL7-era) system
7094 header files (Tom Lane)
7095 <ulink url="&commit_baseurl;db4eba152">&sect;</ulink>
7096 <ulink url="&commit_baseurl;6a5170755">&sect;</ulink>
7097 </para>
7098 </listitem>
7099
7100 <listitem>
7101 <!--
7102 Author: Masahiko Sawada <[email protected]>
7103 Branch: master [85d5bd308] 2025-12-31 11:18:14 -0800
7104 Branch: REL_18_STABLE [640772c6d] 2025-12-31 11:18:17 -0800
7105 -->
7106 <para>
7107 Fix incorrect configure probe
7108 for <function>io_uring_queue_init_mem()</function> (Masahiko Sawada)
7109 <ulink url="&commit_baseurl;640772c6d">&sect;</ulink>
7110 </para>
7111
7112 <para>
7113 This error resulted in failure to optimize async I/O buffer
7114 allocations in autotools-based builds, though the code did work when
7115 building with meson. The main impact of the omission was
7116 slower-than-necessary backend process exits.
7117 </para>
7118 </listitem>
7119
7120 <listitem>
7121 <!--
7122 Author: Thomas Munro <[email protected]>
7123 Branch: master [f94e9141a] 2026-02-06 17:38:49 +1300
7124 Branch: REL_18_STABLE [33e3de6d7] 2026-02-06 17:38:39 +1300
7125 Branch: REL_17_STABLE [4dac22aa1] 2026-02-06 17:41:42 +1300
7126 Branch: REL_16_STABLE [e37b59802] 2026-02-06 17:43:49 +1300
7127 -->
7128 <para>
7129 Add new server parameter <xref linkend="guc-file-extend-method"/> to
7130 control use of <function>posix_fallocate()</function> (Thomas Munro)
7131 <ulink url="&commit_baseurl;33e3de6d7">&sect;</ulink>
7132 </para>
7133
7134 <para>
7135 <productname>PostgreSQL</productname> version 16 and later will
7136 use <function>posix_fallocate()</function>, if the platform provides
7137 it, to extend relation files. However, this has been reported to
7138 interact poorly with some file systems: BTRFS compression is
7139 disabled by the use of <function>posix_fallocate()</function>, and
7140 XFS could produce spurious <literal>ENOSPC</literal> errors in older
7141 Linux kernel versions. To provide a workaround, introduce this new
7142 server parameter. Setting <varname>file_extend_method</varname>
7143 to <literal>write_zeros</literal> will cause the server to return to
7144 the old method of extending files by writing blocks of zeroes.
7145 </para>
7146 </listitem>
7147
7148 <listitem>
7149 <!--
7150 Author: Thomas Munro <[email protected]>
7151 Branch: master [c507ba55f] 2025-12-10 09:01:35 +1300
7152 Branch: REL_18_STABLE [bebb281b0] 2025-12-10 09:05:21 +1300
7153 Branch: REL_17_STABLE [f24af0e04] 2025-12-10 09:10:31 +1300
7154 Branch: REL_16_STABLE [d62a258cd] 2025-12-10 09:11:19 +1300
7155 Branch: master [bec2a0aa3] 2025-12-21 17:34:20 +1300
7156 Branch: REL_18_STABLE [a7d06e74d] 2025-12-21 17:34:49 +1300
7157 Branch: REL_17_STABLE [045185913] 2025-12-21 17:35:46 +1300
7158 Branch: REL_16_STABLE [0666ccc16] 2025-12-21 17:36:04 +1300
7159 Branch: master [45d92b76d] 2025-12-29 15:47:31 +1300
7160 Branch: REL_18_STABLE [4da5c33a3] 2025-12-29 15:48:27 +1300
7161 Branch: REL_17_STABLE [b3c8119e2] 2025-12-29 15:28:17 +1300
7162 Branch: REL_16_STABLE [80e8ec772] 2025-12-29 15:31:39 +1300
7163 -->
7164 <para>
7165 Honor <function>open()</function>'s <literal>O_CLOEXEC</literal>
7166 flag on Windows (Bryan Green, Thomas Munro)
7167 <ulink url="&commit_baseurl;bebb281b0">&sect;</ulink>
7168 <ulink url="&commit_baseurl;a7d06e74d">&sect;</ulink>
7169 <ulink url="&commit_baseurl;4da5c33a3">&sect;</ulink>
7170 </para>
7171
7172 <para>
7173 Make this flag work like it does on POSIX platforms, so that we
7174 don't leak file handles into child processes such as <literal>COPY
7175 TO/FROM PROGRAM</literal>. While that leakage hasn't caused many
7176 problems, it seems undesirable.
7177 </para>
7178 </listitem>
7179
7180 <listitem>
7181 <!--
7182 Author: Tom Lane <[email protected]>
7183 Branch: master [c0bf15729] 2026-02-07 20:05:52 -0500
7184 Branch: REL_18_STABLE [5eac1d68f] 2026-02-07 20:05:52 -0500
7185 Branch: REL_17_STABLE [59c2f7efa] 2026-02-07 20:05:52 -0500
7186 Branch: REL_16_STABLE [7369656fa] 2026-02-07 20:05:52 -0500
7187 -->
7188 <para>
7189 Fix failure to parse long options on the server command line in
7190 Solaris executables built with meson (Tom Lane)
7191 <ulink url="&commit_baseurl;5eac1d68f">&sect;</ulink>
7192 </para>
7193 </listitem>
7194
7195 <listitem>
7196 <!--
7197 Author: Thomas Munro <[email protected]>
7198 Branch: master [32b236644] 2025-11-17 12:48:55 +1300
7199 Branch: REL_18_STABLE [bcfca332f] 2025-11-17 12:48:47 +1300
7200 Branch: REL_17_STABLE [d66a922f9] 2025-11-17 12:48:37 +1300
7201 Branch: REL_16_STABLE [a1407dade] 2025-11-17 12:48:22 +1300
7202 Branch: REL_15_STABLE [3995e4a9d] 2025-11-18 11:19:56 +1300
7203 Branch: REL_14_STABLE [29a3e22f3] 2025-11-18 11:21:15 +1300
7204 -->
7205 <para>
7206 Support process title changes on GNU/Hurd (Michael Banck)
7207 <ulink url="&commit_baseurl;bcfca332f">&sect;</ulink>
7208 </para>
7209 </listitem>
7210
7211 <listitem>
7212 <!--
7213 Author: Masahiko Sawada <[email protected]>
7214 Branch: master [c5c808f9b] 2025-12-24 13:55:29 -0800
7215 Branch: REL_18_STABLE [4e1376900] 2025-12-24 13:55:32 -0800
7216 -->
7217 <para>
7218 Fix <application>psql</application>'s tab completion
7219 for <command>VACUUM</command> option values (Yugo Nagata)
7220 <ulink url="&commit_baseurl;4e1376900">&sect;</ulink>
7221 </para>
7222 </listitem>
7223
7224 <listitem>
7225 <!--
7226 Author: Michael Paquier <[email protected]>
7227 Branch: master [4b77282f2] 2026-01-29 16:20:45 +0900
7228 Branch: REL_18_STABLE [d42735b1e] 2026-01-29 16:20:50 +0900
7229 -->
7230 <para>
7231 In <application>psql</application> command prompts,
7232 do not show a value for <literal>%P</literal> (pipeline status) when
7233 there is no server connection (Chao Li)
7234 <ulink url="&commit_baseurl;d42735b1e">&sect;</ulink>
7235 </para>
7236
7237 <para>
7238 This makes <literal>%P</literal> act like other prompt escape
7239 sequences whose values depend on the active connection.
7240 </para>
7241 </listitem>
7242
7243 <listitem>
7244 <!--
7245 Author: Nathan Bossart <[email protected]>
7246 Branch: master [7a485bd64] 2026-01-09 10:12:54 -0600
7247 Branch: REL_18_STABLE [39d555576] 2026-01-09 10:12:54 -0600
7248 Branch: master [5d1f5079a] 2026-01-11 13:52:50 -0600
7249 Branch: REL_18_STABLE [56e1f5010] 2026-01-11 13:52:50 -0600
7250 -->
7251 <para>
7252 Fix <application>pg_dump</application>'s logic for collecting
7253 sequence values (Nathan Bossart)
7254 <ulink url="&commit_baseurl;39d555576">&sect;</ulink>
7255 <ulink url="&commit_baseurl;56e1f5010">&sect;</ulink>
7256 </para>
7257
7258 <para>
7259 <application>pg_dump</application> failed if a sequence was dropped
7260 concurrently with the dump, even if the sequence was not among the
7261 database objects to be dumped. Also, if the calling user lacks
7262 privileges to read a sequence's
7263 value, <application>pg_dump</application> emitted incorrect values
7264 rather than failing as expected.
7265 </para>
7266 </listitem>
7267
7268 <listitem>
7269 <!--
7270 Author: Daniel Gustafsson <[email protected]>
7271 Branch: master [ec0da9b89] 2025-12-27 23:05:48 +0100
7272 Branch: REL_18_STABLE [61c78e1f4] 2025-12-27 23:05:48 +0100
7273 -->
7274 <para>
7275 Fix potentially-incorrect quoting
7276 of <varname>oauth_validator_libraries</varname> values
7277 by <application>pg_dump</application> (ChangAo Chen)
7278 <ulink url="&commit_baseurl;61c78e1f4">&sect;</ulink>
7279 </para>
7280
7281 <para>
7282 <application>pg_dump</application> applied the wrong quoting rule if
7283 it needed to dump a value of this setting.
7284 </para>
7285 </listitem>
7286
7287 <listitem>
7288 <!--
7289 Author: Noah Misch <[email protected]>
7290 Branch: master [d49936f30] 2025-12-18 10:23:47 -0800
7291 Branch: REL_18_STABLE [573e679a2] 2025-12-18 10:23:51 -0800
7292 Branch: REL_17_STABLE [1cdc07ad5] 2025-12-18 10:23:51 -0800
7293 -->
7294 <para>
7295 Avoid <application>pg_dump</application> assertion failure in
7296 binary-upgrade mode (Vignesh C)
7297 <ulink url="&commit_baseurl;573e679a2">&sect;</ulink>
7298 </para>
7299
7300 <para>
7301 Failure to handle subscription-relation objects in the object
7302 sorting code triggered an assertion, though there were no serious
7303 ill effects in production builds.
7304 </para>
7305 </listitem>
7306
7307 <listitem>
7308 <!--
7309 Author: Fujii Masao <[email protected]>
7310 Branch: master [4aa0ac057] 2025-11-14 22:40:39 +0900
7311 Branch: REL_18_STABLE [00e64e35c] 2025-11-14 22:41:55 +0900
7312 Branch: REL_17_STABLE [5bc251b28] 2025-11-14 22:42:02 +0900
7313 -->
7314 <para>
7315 Fix incorrect error handling in <application>pgbench</application>
7316 with multiple <command>\syncpipeline</command> commands
7317 in pipeline mode (Yugo Nagata)
7318 <ulink url="&commit_baseurl;00e64e35c">&sect;</ulink>
7319 </para>
7320
7321 <para>
7322 If multiple <command>\syncpipeline</command> commands are
7323 encountered after a query error, <application>pgbench</application>
7324 would report <quote>failed to exit pipeline mode</quote>, or get an
7325 assertion failure in an assert-enabled build.
7326 </para>
7327 </listitem>
7328
7329 <listitem>
7330 <!--
7331 Author: Heikki Linnakangas <[email protected]>
7332 Branch: master [d5b4f3a6d] 2025-11-19 18:05:42 +0200
7333 Branch: REL_18_STABLE [19594271c] 2025-11-19 18:06:04 +0200
7334 Branch: REL_17_STABLE [f2e0ca0af] 2025-11-19 18:06:23 +0200
7335 Branch: REL_16_STABLE [890cc81b6] 2025-11-19 18:06:24 +0200
7336 Branch: REL_15_STABLE [7c494072b] 2025-11-19 18:06:26 +0200
7337 Branch: REL_14_STABLE [11cc0f452] 2025-11-19 18:06:27 +0200
7338 -->
7339 <para>
7340 Make <application>pg_resetwal</application> print the updated value
7341 when changing OldestXID (Heikki Linnakangas)
7342 <ulink url="&commit_baseurl;19594271c">&sect;</ulink>
7343 </para>
7344
7345 <para>
7346 It already did that for every other variable it can change.
7347 </para>
7348 </listitem>
7349
7350 <listitem>
7351 <!--
7352 Author: Heikki Linnakangas <[email protected]>
7353 Branch: master [94939c5f3] 2025-11-12 12:20:16 +0200
7354 Branch: REL_18_STABLE [8747b969f] 2025-11-12 12:21:30 +0200
7355 Branch: REL_17_STABLE [cb2ef0e92] 2025-11-12 12:23:55 +0200
7356 Branch: REL_16_STABLE [e039b09f8] 2025-11-12 12:45:16 +0200
7357 Branch: REL_15_STABLE [97cd4b65a] 2025-11-12 12:46:19 +0200
7358 -->
7359 <para>
7360 Make <application>pg_resetwal</application> allow setting next
7361 multixact xid to 0 or next multixact offset to UINT32_MAX (Maxim
7362 Orlov)
7363 <ulink url="&commit_baseurl;8747b969f">&sect;</ulink>
7364 </para>
7365
7366 <para>
7367 These are valid values, so rejecting them was incorrect. In the
7368 worst case, if a pg_upgrade is attempted when exactly at the point
7369 of multixact wraparound, the upgrade would fail.
7370 </para>
7371 </listitem>
7372
7373 <listitem>
7374 <!--
7375 Author: Álvaro Herrera <[email protected]>
7376 Branch: master [6bd469d26] 2025-12-04 18:12:08 +0100
7377 Branch: REL_18_STABLE [df93f94dd] 2025-12-04 18:12:08 +0100
7378 Branch: REL_17_STABLE [ce2f575b7] 2025-12-04 18:12:08 +0100
7379 Branch: master [1f28982e4] 2026-01-21 18:55:43 +0100
7380 Branch: REL_18_STABLE [3c83a2a0a] 2026-01-21 18:55:43 +0100
7381 Branch: REL_17_STABLE [e1a327dc4] 2026-01-21 18:55:43 +0100
7382 Branch: REL_16_STABLE [098a1fab8] 2026-01-21 18:55:43 +0100
7383 Branch: REL_15_STABLE [dcddd6987] 2026-01-21 18:55:43 +0100
7384 Branch: REL_14_STABLE [607a67c5e] 2026-01-21 18:55:43 +0100
7385 -->
7386 <para>
7387 In <filename>contrib/amcheck</filename>, use the correct snapshot
7388 for btree index parent checks (Mihail Nikalayeu)
7389 <ulink url="&commit_baseurl;df93f94dd">&sect;</ulink>
7390 <ulink url="&commit_baseurl;3c83a2a0a">&sect;</ulink>
7391 </para>
7392
7393 <para>
7394 The previous coding caused spurious errors when examining indexes
7395 created with <command>CREATE INDEX CONCURRENTLY</command>.
7396 </para>
7397 </listitem>
7398
7399 <listitem>
7400 <!--
7401 Author: Heikki Linnakangas <[email protected]>
7402 Branch: master [cbe04e5d7] 2025-12-02 21:11:15 +0200
7403 Branch: REL_18_STABLE [19e786727] 2025-12-02 21:15:04 +0200
7404 Branch: REL_17_STABLE [e8ae59445] 2025-12-02 21:15:28 +0200
7405 Branch: REL_16_STABLE [182901626] 2025-12-02 21:15:48 +0200
7406 Branch: REL_15_STABLE [7792bdc45] 2025-12-02 21:16:06 +0200
7407 Branch: REL_14_STABLE [fbb4b6078] 2025-12-02 21:16:17 +0200
7408 -->
7409 <para>
7410 Fix <filename>contrib/amcheck</filename> to
7411 handle <quote>half-dead</quote> btree index pages correctly
7412 (Heikki Linnakangas)
7413 <ulink url="&commit_baseurl;19e786727">&sect;</ulink>
7414 </para>
7415
7416 <para>
7417 <filename>amcheck</filename> expected such a page to have a parent
7418 downlink, but it does not, leading to a false error report
7419 about <quote>mismatch between parent key and child high key</quote>.
7420 </para>
7421 </listitem>
7422
7423 <listitem>
7424 <!--
7425 Author: Heikki Linnakangas <[email protected]>
7426 Branch: master [6c05ef572] 2025-12-02 21:10:51 +0200
7427 Branch: REL_18_STABLE [50c63ebb0] 2025-12-02 21:14:53 +0200
7428 Branch: REL_17_STABLE [5a2d1df00] 2025-12-02 21:15:19 +0200
7429 Branch: REL_16_STABLE [f2a6df9fd] 2025-12-02 21:15:43 +0200
7430 Branch: REL_15_STABLE [721b58fbe] 2025-12-02 21:16:01 +0200
7431 Branch: REL_14_STABLE [a4cb21ea9] 2025-12-02 21:16:13 +0200
7432 -->
7433 <para>
7434 Fix <filename>contrib/amcheck</filename> to
7435 handle incomplete btree root page splits correctly
7436 (Heikki Linnakangas)
7437 <ulink url="&commit_baseurl;50c63ebb0">&sect;</ulink>
7438 </para>
7439
7440 <para>
7441 <filename>amcheck</filename> could report a false error
7442 about <quote>block is not true root</quote>.
7443 </para>
7444 </listitem>
7445
7446 <listitem>
7447 <!--
7448 Author: Michael Paquier <[email protected]>
7449 Branch: master [3f83de20b] 2025-12-11 14:11:06 +0900
7450 Branch: REL_18_STABLE [580b5c2f3] 2025-12-11 14:11:25 +0900
7451 -->
7452 <para>
7453 Fix excessive memory allocation
7454 in <filename>contrib/pg_buffercache</filename> (David Geier)
7455 <ulink url="&commit_baseurl;580b5c2f3">&sect;</ulink>
7456 </para>
7457
7458 <para>
7459 The code allocated twice as much memory as it needed for NUMA
7460 page status.
7461 </para>
7462 </listitem>
7463
7464 <listitem>
7465 <!--
7466 Author: David Rowley <[email protected]>
7467 Branch: master [4f49e4b55] 2026-01-04 20:32:40 +1300
7468 Branch: REL_18_STABLE [07c1c6ec5] 2026-01-04 20:33:14 +1300
7469 Branch: REL_17_STABLE [a5f2dc421] 2026-01-04 20:33:39 +1300
7470 Branch: REL_16_STABLE [54f82c4aa] 2026-01-04 20:34:01 +1300
7471 Branch: REL_15_STABLE [c89510431] 2026-01-04 20:34:22 +1300
7472 Branch: REL_14_STABLE [67a6fd507] 2026-01-04 20:34:45 +1300
7473 -->
7474 <para>
7475 Fix edge-case integer overflow
7476 in <filename>contrib/intarray</filename>'s selectivity estimator
7477 for <literal>@@</literal> (Chao Li)
7478 <ulink url="&commit_baseurl;07c1c6ec5">&sect;</ulink>
7479 </para>
7480
7481 <para>
7482 This could cause poor selectivity estimates to be produced for cases
7483 involving the maximum integer value.
7484 </para>
7485 </listitem>
7486
7487 <listitem>
7488 <!--
7489 Author: Jeff Davis <[email protected]>
7490 Branch: master [84d5efa7e] 2025-12-16 10:35:40 -0800
7491 Branch: REL_18_STABLE [f79e239e0] 2025-12-16 10:36:09 -0800
7492 Branch: REL_17_STABLE [b8cfe9dc2] 2025-12-16 10:36:29 -0800
7493 Branch: REL_16_STABLE [b80227c0a] 2025-12-16 10:36:48 -0800
7494 Branch: REL_15_STABLE [335b2f30b] 2025-12-16 10:37:22 -0800
7495 Branch: REL_14_STABLE [898991966] 2025-12-16 10:38:15 -0800
7496 -->
7497 <para>
7498 Fix multibyte-encoding issue in <filename>contrib/ltree</filename>
7499 (Jeff Davis)
7500 <ulink url="&commit_baseurl;f79e239e0">&sect;</ulink>
7501 </para>
7502
7503 <para>
7504 The previous coding could pass an incomplete multibyte character
7505 to <function>lower()</function>, probably resulting in incorrect
7506 behavior.
7507 </para>
7508 </listitem>
7509
7510 <listitem>
7511 <!--
7512 Author: Michael Paquier <[email protected]>
7513 Branch: master [5d95219fa] 2026-01-20 08:11:12 +0900
7514 Branch: REL_18_STABLE [3304e97b1] 2026-01-20 08:11:16 +0900
7515 -->
7516 <para>
7517 Avoid crash in <filename>contrib/pg_stat_statements</filename> when
7518 an <literal>IN</literal> list contains both constants and
7519 non-constant expressions (Sami Imseih)
7520 <ulink url="&commit_baseurl;3304e97b1">&sect;</ulink>
7521 </para>
7522 </listitem>
7523
7524 <listitem>
7525 <!--
7526 Author: Tom Lane <[email protected]>
7527 Branch: master [228fe0c3e] 2026-01-18 14:54:33 -0500
7528 Branch: REL_18_STABLE [6574bee64] 2026-01-18 14:54:47 -0500
7529 Branch: REL_17_STABLE [f87c0b84e] 2026-01-18 14:54:54 -0500
7530 Branch: REL_16_STABLE [d852d105e] 2026-01-18 14:55:01 -0500
7531 Branch: REL_15_STABLE [00410b76d] 2026-01-18 14:55:07 -0500
7532 Branch: REL_14_STABLE [8bbf28191] 2026-01-18 14:55:13 -0500
7533 -->
7534 <para>
7535 Update time zone data files to <application>tzdata</application>
7536 release 2025c (Tom Lane)
7537 <ulink url="&commit_baseurl;6574bee64">&sect;</ulink>
7538 </para>
7539
7540 <para>
7541 The only change is in historical data for pre-1976 timestamps in
7542 Baja California.
7543 </para>
7544 </listitem>
7545
7546 </itemizedlist>
7547
7548 </sect2>
7549 </sect1>
7550
7551 <sect1 id="release-18-1">
7552 <title>Release 18.1</title>
7553
7554 <formalpara>
7555 <title>Release date:</title>
7556 <para>2025-11-13</para>
7557 </formalpara>
7558
7559 <para>
7560 This release contains a variety of fixes from 18.0.
7561 For information about new features in major release 18, see
7562 <xref linkend="release-18"/>.
7563 </para>
7564
7565 <sect2 id="release-18-1-migration">
7566 <title>Migration to Version 18.1</title>
7567
7568 <para>
7569 A dump/restore is not required for those running 18.X.
7570 </para>
7571 </sect2>
7572
7573 <sect2 id="release-18-1-changes">
7574 <title>Changes</title>
7575
7576 <itemizedlist>
7577
7578 <listitem>
7579 <!--
7580 Author: Nathan Bossart <[email protected]>
7581 Branch: master [5e4fcbe53] 2025-11-10 09:00:00 -0600
7582 Branch: REL_18_STABLE [00eb646ea] 2025-11-10 09:00:00 -0600
7583 Branch: REL_17_STABLE [e2fb3dfa8] 2025-11-10 09:00:00 -0600
7584 Branch: REL_16_STABLE [d20abb587] 2025-11-10 09:00:00 -0600
7585 Branch: REL_15_STABLE [2393d374a] 2025-11-10 09:00:00 -0600
7586 Branch: REL_14_STABLE [95cce5669] 2025-11-10 09:00:00 -0600
7587 Branch: REL_13_STABLE [8a2530ebc] 2025-11-10 09:00:00 -0600
7588 -->
7589 <para>
7590 Check for <literal>CREATE</literal> privileges on the schema
7591 in <command>CREATE STATISTICS</command> (Jelte Fennema-Nio)
7592 <ulink url="&commit_baseurl;00eb646ea">&sect;</ulink>
7593 </para>
7594
7595 <para>
7596 This omission allowed table owners to create statistics in any
7597 schema, potentially leading to unexpected naming conflicts.
7598 </para>
7599
7600 <para>
7601 The <productname>PostgreSQL</productname> Project thanks
7602 Jelte Fennema-Nio for reporting this problem.
7603 (CVE-2025-12817)
7604 </para>
7605 </listitem>
7606
7607 <listitem>
7608 <!--
7609 Author: Jacob Champion <[email protected]>
7610 Branch: master [600086f47] 2025-11-10 06:20:33 -0800
7611 Branch: REL_18_STABLE [7eb8fcad8] 2025-11-10 06:03:01 -0800
7612 Branch: REL_17_STABLE [f5999f018] 2025-11-10 06:03:03 -0800
7613 Branch: REL_16_STABLE [585fd9b3c] 2025-11-10 06:03:04 -0800
7614 Branch: REL_15_STABLE [91421565f] 2025-11-10 06:03:05 -0800
7615 Branch: REL_14_STABLE [96d2c7e96] 2025-11-10 06:03:05 -0800
7616 Branch: REL_13_STABLE [d6f0c0d6d] 2025-11-10 06:03:06 -0800
7617 -->
7618 <para>
7619 Avoid integer overflow in allocation-size calculations
7620 within <application>libpq</application> (Jacob Champion)
7621 <ulink url="&commit_baseurl;7eb8fcad8">&sect;</ulink>
7622 </para>
7623
7624 <para>
7625 Several places in <application>libpq</application> were not
7626 sufficiently careful about computing the required size of a memory
7627 allocation. Sufficiently large inputs could cause integer overflow,
7628 resulting in an undersized buffer, which would then lead to writing
7629 past the end of the buffer.
7630 </para>
7631
7632 <para>
7633 The <productname>PostgreSQL</productname> Project thanks Aleksey
7634 Solovev of Positive Technologies for reporting this problem.
7635 (CVE-2025-12818)
7636 </para>
7637 </listitem>
7638
7639 <listitem>
7640 <!--
7641 Author: Amit Langote <[email protected]>
7642 Branch: master [ef5e60a9d] 2025-10-09 01:07:59 -0400
7643 Branch: REL_18_STABLE [dc9125111] 2025-10-09 01:07:52 -0400
7644 Branch: REL_17_STABLE [09f86a42f] 2025-10-09 01:07:36 -0400
7645 Author: Peter Eisentraut <[email protected]>
7646 Branch: master [c09a06918] 2025-11-04 12:25:04 +0100
7647 Branch: REL_18_STABLE [1baae827e] 2025-11-04 12:25:14 +0100
7648 Branch: REL_17_STABLE [1e6dfdaa0] 2025-11-04 12:25:20 +0100
7649 -->
7650 <para>
7651 Prevent <quote>unrecognized node type</quote> errors when a SQL/JSON
7652 function such as <function>JSON_VALUE</function> has
7653 a <literal>DEFAULT</literal> clause containing
7654 a <literal>COLLATE</literal> expression (Jian He)
7655 <ulink url="&commit_baseurl;dc9125111">&sect;</ulink>
7656 <ulink url="&commit_baseurl;1baae827e">&sect;</ulink>
7657 </para>
7658 </listitem>
7659
7660 <listitem>
7661 <!--
7662 Author: Richard Guo <[email protected]>
7663 Branch: master [18d261409] 2025-10-21 12:35:36 +0900
7664 Branch: REL_18_STABLE [40c242830] 2025-10-21 12:38:16 +0900
7665 Branch: REL_18_STABLE [ee49f2cf4] 2025-10-21 14:12:13 +0900
7666 -->
7667 <para>
7668 Avoid incorrect optimization of
7669 variable-free <literal>HAVING</literal> clauses with grouping sets
7670 (Richard Guo)
7671 <ulink url="&commit_baseurl;40c242830">&sect;</ulink>
7672 <ulink url="&commit_baseurl;ee49f2cf4">&sect;</ulink>
7673 </para>
7674 </listitem>
7675
7676 <listitem>
7677 <!--
7678 Author: Richard Guo <[email protected]>
7679 Branch: master [257ee7834] 2025-10-30 11:58:45 +0900
7680 Branch: REL_18_STABLE [ef6168baf] 2025-10-30 12:03:15 +0900
7681 -->
7682 <para>
7683 Do not use parallelism in hash right semi joins (Richard Guo)
7684 <ulink url="&commit_baseurl;ef6168baf">&sect;</ulink>
7685 </para>
7686
7687 <para>
7688 The case does not work reliably due to a race condition in updating
7689 the join's shared hash table.
7690 </para>
7691 </listitem>
7692
7693 <listitem>
7694 <!--
7695 Author: Richard Guo <[email protected]>
7696 Branch: master [c1777f2d6] 2025-11-05 18:09:21 +0900
7697 Branch: REL_18_STABLE [500f64636] 2025-11-05 18:15:02 +0900
7698 -->
7699 <para>
7700 Avoid possible division-by-zero when creating ordered-append plans
7701 (Richard Guo)
7702 <ulink url="&commit_baseurl;500f64636">&sect;</ulink>
7703 </para>
7704
7705 <para>
7706 This mistake could result in incorrect selection of the cheapest
7707 path, or in an assertion failure in debug builds.
7708 </para>
7709 </listitem>
7710
7711 <listitem>
7712 <!--
7713 Author: Peter Eisentraut <[email protected]>
7714 Branch: master [35e53b684] 2025-10-28 10:07:29 +0100
7715 Branch: REL_18_STABLE [74197bdc8] 2025-10-28 10:11:35 +0100
7716 -->
7717 <para>
7718 Fix planner failure with index types that can do ordered access but
7719 not index-only scans (Maxime Schoemans)
7720 <ulink url="&commit_baseurl;74197bdc8">&sect;</ulink>
7721 </para>
7722
7723 <para>
7724 This oversight resulted in errors like <quote>no data returned for
7725 index-only scan</quote>. The case does not arise with any in-core
7726 index type, but some extensions encountered the problem.
7727 </para>
7728 </listitem>
7729
7730 <listitem>
7731 <!--
7732 Author: Peter Geoghegan <[email protected]>
7733 Branch: master [843e50208] 2025-10-10 14:52:25 -0400
7734 Branch: REL_18_STABLE [61de81a49] 2025-10-10 14:52:23 -0400
7735 Branch: REL_17_STABLE [ae15cebc2] 2025-10-10 14:52:21 -0400
7736 Branch: REL_16_STABLE [c160fd469] 2025-10-10 14:52:19 -0400
7737 Branch: REL_15_STABLE [ca0c93908] 2025-10-10 14:52:17 -0400
7738 Branch: REL_14_STABLE [314004021] 2025-10-10 14:52:14 -0400
7739 Branch: REL_13_STABLE [af302ff6b] 2025-10-10 14:52:12 -0400
7740 -->
7741 <para>
7742 Remove faulty assertion in btree index cleanup (Peter Geoghegan)
7743 <ulink url="&commit_baseurl;61de81a49">&sect;</ulink>
7744 </para>
7745 </listitem>
7746
7747 <listitem>
7748 <!--
7749 Author: Tomas Vondra <[email protected]>
7750 Branch: master [c98dffcb7] 2025-11-04 18:51:17 +0100
7751 Branch: REL_18_STABLE [a26b753a0] 2025-11-04 18:47:14 +0100
7752 -->
7753 <para>
7754 Avoid possible out-of-memory or <quote>invalid memory alloc request
7755 size</quote> failures during parallel GIN index build (Tomas Vondra)
7756 <ulink url="&commit_baseurl;a26b753a0">&sect;</ulink>
7757 </para>
7758 </listitem>
7759
7760 <listitem>
7761 <!--
7762 Author: Álvaro Herrera <[email protected]>
7763 Branch: master [a95e3d84c] 2025-11-04 13:23:26 +0100
7764 Branch: REL_18_STABLE [419ffde23] 2025-11-04 13:23:26 +0100
7765 Branch: REL_17_STABLE [f4b68b033] 2025-11-04 13:23:26 +0100
7766 Branch: REL_16_STABLE [6ef33c805] 2025-11-04 13:23:26 +0100
7767 Branch: REL_15_STABLE [23ddadf68] 2025-11-04 13:23:26 +0100
7768 Branch: REL_14_STABLE [f0ad41716] 2025-11-04 13:23:26 +0100
7769 Branch: REL_13_STABLE [3c7b47974] 2025-11-04 13:23:26 +0100
7770 Branch: master [0a3d27bfe] 2025-11-04 20:31:43 +0100
7771 Branch: REL_18_STABLE [8733f0b54] 2025-11-04 20:31:43 +0100
7772 Branch: REL_17_STABLE [3b5007347] 2025-11-04 20:31:43 +0100
7773 Branch: REL_16_STABLE [20442cf50] 2025-11-04 20:31:43 +0100
7774 Branch: REL_15_STABLE [bcfbd3f74] 2025-11-04 20:31:43 +0100
7775 Branch: REL_14_STABLE [65b0d1f74] 2025-11-04 20:31:43 +0100
7776 Branch: REL_13_STABLE [ef81697fe] 2025-11-04 20:31:43 +0100
7777 -->
7778 <para>
7779 Ensure that BRIN autosummarization provides a snapshot for index
7780 expressions that need one (Álvaro Herrera)
7781 <ulink url="&commit_baseurl;419ffde23">&sect;</ulink>
7782 <ulink url="&commit_baseurl;8733f0b54">&sect;</ulink>
7783 </para>
7784
7785 <para>
7786 Previously, autosummarization would fail for such indexes, and then
7787 leave placeholder index tuples behind, causing the index to bloat
7788 over time.
7789 </para>
7790 </listitem>
7791
7792 <listitem>
7793 <!--
7794 Author: David Rowley <[email protected]>
7795 Branch: master [9fd29d7ff] 2025-10-21 20:46:14 +1300
7796 Branch: REL_18_STABLE [715983a81] 2025-10-21 20:46:49 +1300
7797 Branch: REL_17_STABLE [c4f5a59ab] 2025-10-21 20:47:10 +1300
7798 Branch: REL_16_STABLE [ef915bf93] 2025-10-21 20:47:35 +1300
7799 Branch: REL_15_STABLE [810aaf7f2] 2025-10-21 20:48:06 +1300
7800 Branch: REL_14_STABLE [eea24eb0a] 2025-10-21 20:48:34 +1300
7801 Branch: REL_13_STABLE [c28f8ca29] 2025-10-21 20:49:00 +1300
7802 -->
7803 <para>
7804 Fix integer-overflow hazard in BRIN index scans when the table
7805 contains close to 2<superscript>32</superscript> pages (Sunil S)
7806 <ulink url="&commit_baseurl;715983a81">&sect;</ulink>
7807 </para>
7808
7809 <para>
7810 This oversight could result in an infinite loop or scanning of
7811 unneeded table pages.
7812 </para>
7813 </listitem>
7814
7815 <listitem>
7816 <!--
7817 Author: David Rowley <[email protected]>
7818 Branch: master [6911f8037] 2025-10-23 13:11:02 +1300
7819 Branch: REL_18_STABLE [ceb51d09b] 2025-10-23 13:12:03 +1300
7820 Branch: REL_17_STABLE [10945148e] 2025-10-23 13:12:49 +1300
7821 Branch: REL_16_STABLE [3398b0d02] 2025-10-23 13:13:19 +1300
7822 Branch: REL_15_STABLE [b8ecfbe5a] 2025-10-23 13:13:44 +1300
7823 Branch: REL_14_STABLE [e4316ec4d] 2025-10-23 13:14:08 +1300
7824 Branch: REL_13_STABLE [4afab175b] 2025-10-23 13:14:33 +1300
7825 -->
7826 <para>
7827 Fix incorrect zero-extension of stored values in JIT-generated tuple
7828 deforming code (David Rowley)
7829 <ulink url="&commit_baseurl;ceb51d09b">&sect;</ulink>
7830 </para>
7831
7832 <para>
7833 When not using JIT, the equivalent code does sign-extension not
7834 zero-extension, leading to a different Datum representation of small
7835 integer data types. This inconsistency was masked in most cases,
7836 but it is known to lead to <quote>could not find memoization table
7837 entry</quote> errors when using Memoize plan nodes, and there might
7838 be other symptoms.
7839 </para>
7840 </listitem>
7841
7842 <listitem>
7843 <!--
7844 Author: David Rowley <[email protected]>
7845 Branch: master [5c0a20003] 2025-10-18 16:07:04 +1300
7846 Branch: REL_18_STABLE [0b6a02f03] 2025-10-18 16:07:41 +1300
7847 -->
7848 <para>
7849 Fix rare crash when processing hashed <literal>GROUPING
7850 SETS</literal> queries (David Rowley)
7851 <ulink url="&commit_baseurl;0b6a02f03">&sect;</ulink>
7852 </para>
7853 </listitem>
7854
7855 <listitem>
7856 <!--
7857 Author: Tomas Vondra <[email protected]>
7858 Branch: master [b85c4700f] 2025-10-17 22:21:50 +0200
7859 Branch: REL_18_STABLE [aa151022e] 2025-10-17 22:27:49 +0200
7860 -->
7861 <para>
7862 Repair faulty hash-table-size-choosing logic in hash joins
7863 (Tomas Vondra)
7864 <ulink url="&commit_baseurl;aa151022e">&sect;</ulink>
7865 </para>
7866
7867 <para>
7868 Hash joins sometimes used more memory than intended, or failed to
7869 divide it in an efficient way.
7870 </para>
7871 </listitem>
7872
7873 <listitem>
7874 <!--
7875 Author: Nathan Bossart <[email protected]>
7876 Branch: master [688dc6299] 2025-10-15 12:47:33 -0500
7877 Branch: REL_18_STABLE [c8af5019b] 2025-10-15 12:47:33 -0500
7878 Branch: REL_18_STABLE [15d7dded0] 2025-10-15 13:14:00 -0500
7879 -->
7880 <para>
7881 Improve relation lookup logic in statistics manipulation functions
7882 (Nathan Bossart)
7883 <ulink url="&commit_baseurl;c8af5019b">&sect;</ulink>
7884 <ulink url="&commit_baseurl;15d7dded0">&sect;</ulink>
7885 </para>
7886
7887 <para>
7888 Fix <function>pg_restore_relation_stats()</function>,
7889 <function>pg_clear_relation_stats()</function>,
7890 <function>pg_restore_attribute_stats()</function>, and
7891 <function>pg_clear_attribute_stats()</function> to check
7892 privileges before acquiring lock on the target relation
7893 rather than after.
7894 </para>
7895 </listitem>
7896
7897 <listitem>
7898 <!--
7899 Author: David Rowley <[email protected]>
7900 Branch: master [39dcfda2d] 2025-10-26 10:59:50 +1300
7901 Branch: REL_18_STABLE [a2387c32f] 2025-10-26 11:01:32 +1300
7902 Branch: REL_17_STABLE [0d3074615] 2025-10-26 11:01:53 +1300
7903 Branch: REL_16_STABLE [a546964db] 2025-10-26 11:02:15 +1300
7904 Branch: REL_15_STABLE [2992b9a07] 2025-10-26 11:02:36 +1300
7905 -->
7906 <para>
7907 Fix incorrect logic for caching result-relation information for
7908 triggers (David Rowley, Amit Langote)
7909 <ulink url="&commit_baseurl;a2387c32f">&sect;</ulink>
7910 </para>
7911
7912 <para>
7913 In cases where partitions' column sets aren't physically identical
7914 to their parent partitioned tables' column sets, this oversight
7915 could lead to crashes.
7916 </para>
7917 </listitem>
7918
7919 <listitem>
7920 <!--
7921 Author: Amit Langote <[email protected]>
7922 Branch: master [905e932f0] 2025-10-16 14:01:44 +0900
7923 Branch: REL_18_STABLE [1296dcf18] 2025-10-16 14:01:50 +0900
7924 -->
7925 <para>
7926 Fix crash during EvalPlanQual rechecks on partitioned tables (David
7927 Rowley, Amit Langote)
7928 <ulink url="&commit_baseurl;1296dcf18">&sect;</ulink>
7929 </para>
7930 </listitem>
7931
7932 <listitem>
7933 <!--
7934 Author: Etsuro Fujita <[email protected]>
7935 Branch: master [12609fbac] 2025-10-15 17:15:00 +0900
7936 Branch: REL_18_STABLE [b14144325] 2025-10-15 17:15:01 +0900
7937 Branch: REL_17_STABLE [2bb84ea7e] 2025-10-15 17:15:02 +0900
7938 Branch: REL_16_STABLE [5a9af4868] 2025-10-15 17:15:03 +0900
7939 Branch: REL_15_STABLE [4a08603a2] 2025-10-15 17:15:04 +0900
7940 Branch: REL_14_STABLE [24e74b962] 2025-10-15 17:15:05 +0900
7941 Branch: REL_13_STABLE [12b0c0e51] 2025-10-15 17:15:05 +0900
7942 -->
7943 <para>
7944 Fix EvalPlanQual handling of foreign or custom joins that do not
7945 have an alternative local-join plan prepared for EPQ (Masahiko
7946 Sawada, Etsuro Fujita)
7947 <ulink url="&commit_baseurl;b14144325">&sect;</ulink>
7948 </para>
7949
7950 <para>
7951 In such cases the foreign or custom access method should be invoked
7952 normally, but that did not happen, typically leading to a crash.
7953 </para>
7954 </listitem>
7955
7956 <listitem>
7957 <!--
7958 Author: Álvaro Herrera <[email protected]>
7959 Branch: master [3231fd045] 2025-10-11 20:30:12 +0200
7960 Branch: REL_18_STABLE [08c037dff] 2025-10-11 20:30:12 +0200
7961 Branch: REL_17_STABLE [ea06f97ee] 2025-10-11 20:30:12 +0200
7962 Branch: REL_16_STABLE [b835759ec] 2025-10-11 20:30:12 +0200
7963 Branch: REL_15_STABLE [bdae98495] 2025-10-11 20:30:12 +0200
7964 Branch: REL_14_STABLE [b753be38a] 2025-10-11 20:30:12 +0200
7965 -->
7966 <para>
7967 Avoid duplicating hash partition constraints during <literal>DETACH
7968 CONCURRENTLY</literal> (Haiyang Li)
7969 <ulink url="&commit_baseurl;08c037dff">&sect;</ulink>
7970 </para>
7971
7972 <para>
7973 <command>ALTER TABLE DETACH PARTITION CONCURRENTLY</command> was
7974 written to add a copy of the partitioning constraint to the
7975 now-detached partition. This was misguided, partially because
7976 non-concurrent <literal>DETACH</literal> doesn't do that, but mostly
7977 because in the case of hash partitioning the constraint expression
7978 contains references to the parent table's OID. That causes problems
7979 during dump/restore, or if the parent table is dropped
7980 after <literal>DETACH</literal>. In v19 and later, we'll no longer
7981 create any such copied constraints at all. In released branches, to
7982 minimize the risk of unforeseen consequences, only skip adding a
7983 copied constraint if it is for hash partitioning.
7984 </para>
7985 </listitem>
7986
7987 <listitem>
7988 <!--
7989 Author: Peter Eisentraut <[email protected]>
7990 Branch: master [040cc5f3c] 2025-11-04 14:46:58 +0100
7991 Branch: REL_18_STABLE [ba99c9491] 2025-11-04 14:47:15 +0100
7992 Branch: REL_17_STABLE [0b44f2443] 2025-11-04 15:18:09 +0100
7993 Branch: REL_16_STABLE [7180d56c5] 2025-11-04 15:22:17 +0100
7994 Branch: REL_15_STABLE [643a5e96c] 2025-11-04 15:28:46 +0100
7995 Branch: REL_14_STABLE [04345d7a4] 2025-11-04 15:37:08 +0100
7996 Branch: REL_13_STABLE [7f239c72a] 2025-11-04 15:37:19 +0100
7997 -->
7998 <para>
7999 Disallow generated columns in partition keys
8000 (Jian He, Ashutosh Bapat)
8001 <ulink url="&commit_baseurl;ba99c9491">&sect;</ulink>
8002 </para>
8003
8004 <para>
8005 This was already not allowed, but the check missed some cases, such
8006 as where the column reference is implicit in a whole-row reference.
8007 </para>
8008 </listitem>
8009
8010 <listitem>
8011 <!--
8012 Author: Peter Eisentraut <[email protected]>
8013 Branch: master [aa606b931] 2025-11-06 13:54:42 +0100
8014 Branch: REL_18_STABLE [0f9e0068b] 2025-11-06 13:55:08 +0100
8015 Branch: REL_17_STABLE [07f787e57] 2025-11-06 14:01:42 +0100
8016 Branch: REL_16_STABLE [26958f4d9] 2025-11-06 14:01:57 +0100
8017 Branch: REL_15_STABLE [8278737bf] 2025-11-06 14:02:03 +0100
8018 Branch: REL_14_STABLE [ccfe28eb4] 2025-11-06 14:02:09 +0100
8019 Branch: REL_13_STABLE [3717849e6] 2025-11-06 14:02:13 +0100
8020 -->
8021 <para>
8022 Disallow generated columns in <literal>COPY ... FROM
8023 ... WHERE</literal> clauses (Peter Eisentraut, Jian He)
8024 <ulink url="&commit_baseurl;0f9e0068b">&sect;</ulink>
8025 </para>
8026
8027 <para>
8028 Previously, incorrect behavior or an obscure error message resulted
8029 from attempting to reference such a column, since generated columns
8030 have not yet been computed at the point
8031 where <literal>WHERE</literal> filtering is done.
8032 </para>
8033 </listitem>
8034
8035 <listitem>
8036 <!--
8037 Author: Álvaro Herrera <[email protected]>
8038 Branch: master [cf8be0225] 2025-11-03 15:58:19 +0100
8039 Branch: REL_18_STABLE [d9ffc2729] 2025-11-03 15:58:19 +0100
8040 -->
8041 <para>
8042 Prevent setting a column as identity if it has a not-null constraint
8043 but the constraint is marked as invalid (Jian He)
8044 <ulink url="&commit_baseurl;d9ffc2729">&sect;</ulink>
8045 </para>
8046
8047 <para>
8048 Identity columns must be not-null, but the check for that missed
8049 this edge case.
8050 </para>
8051 </listitem>
8052
8053 <listitem>
8054 <!--
8055 Author: John Naylor <[email protected]>
8056 Branch: master [54ab74865] 2025-10-03 16:05:02 +0700
8057 Branch: REL_18_STABLE [76613b539] 2025-10-03 16:07:42 +0700
8058 Branch: REL_17_STABLE [3549ffb6a] 2025-10-03 16:07:34 +0700
8059 -->
8060 <para>
8061 Avoid potential use-after-free in parallel vacuum (Kevin Oommen
8062 Anish)
8063 <ulink url="&commit_baseurl;76613b539">&sect;</ulink>
8064 </para>
8065
8066 <para>
8067 This bug seems to have no consequences in standard builds, but it's
8068 theoretically a hazard.
8069 </para>
8070 </listitem>
8071
8072 <listitem>
8073 <!--
8074 Author: Noah Misch <[email protected]>
8075 Branch: master [a95393ecd] 2025-09-29 11:15:44 -0700
8076 Branch: REL_18_STABLE [d024160ff] 2025-09-29 11:15:47 -0700
8077 Branch: REL_17_STABLE [6778fbca6] 2025-09-29 11:15:48 -0700
8078 Branch: REL_16_STABLE [ab16418ee] 2025-09-29 11:15:48 -0700
8079 Branch: REL_15_STABLE [d202ec1fb] 2025-09-29 11:15:48 -0700
8080 Branch: REL_14_STABLE [5816baa9b] 2025-09-29 11:15:49 -0700
8081 Branch: REL_13_STABLE [afb2cce74] 2025-09-29 11:15:49 -0700
8082 -->
8083 <para>
8084 Fix visibility checking for statistics objects
8085 in <literal>pg_temp</literal> (Noah Misch)
8086 <ulink url="&commit_baseurl;d024160ff">&sect;</ulink>
8087 </para>
8088
8089 <para>
8090 A statistics object located in a temporary schema cannot be named
8091 without schema qualification,
8092 but <function>pg_statistics_obj_is_visible()</function> missed that
8093 memo and could return <quote>true</quote> regardless. In turn,
8094 functions such as <function>pg_describe_object()</function> could
8095 fail to schema-qualify the object's name as expected.
8096 </para>
8097 </listitem>
8098
8099 <listitem>
8100 <!--
8101 Author: Álvaro Herrera <[email protected]>
8102 Branch: master [ff47f9c16] 2025-10-11 16:39:22 +0200
8103 Branch: REL_18_STABLE [33e7b4a7c] 2025-10-11 16:39:22 +0200
8104 Branch: REL_17_STABLE [f9993ac64] 2025-10-11 16:39:22 +0200
8105 Branch: REL_16_STABLE [c72b5c536] 2025-10-11 16:39:22 +0200
8106 Branch: REL_15_STABLE [23b316c36] 2025-10-11 16:39:22 +0200
8107 -->
8108 <para>
8109 Fix minor memory leak during WAL replay of database creation
8110 (Nathan Bossart)
8111 <ulink url="&commit_baseurl;33e7b4a7c">&sect;</ulink>
8112 </para>
8113 </listitem>
8114
8115 <listitem>
8116 <!--
8117 Author: Fujii Masao <[email protected]>
8118 Branch: master [883a95646] 2025-10-22 11:27:15 +0900
8119 Branch: REL_18_STABLE [9670032cc] 2025-10-22 11:28:48 +0900
8120 Branch: REL_17_STABLE [62d5ee75b] 2025-10-22 11:28:57 +0900
8121 Branch: REL_16_STABLE [2e55cf4ef] 2025-10-22 11:29:02 +0900
8122 Branch: REL_15_STABLE [59b215f72] 2025-10-22 11:29:07 +0900
8123 Branch: REL_14_STABLE [a7ab6ce6a] 2025-10-22 11:29:13 +0900
8124 Branch: REL_13_STABLE [7d7ebdb80] 2025-10-22 11:29:18 +0900
8125 -->
8126 <para>
8127 Fix incorrect reporting of replication lag
8128 in <structname>pg_stat_replication</structname> view (Fujii Masao)
8129 <ulink url="&commit_baseurl;9670032cc">&sect;</ulink>
8130 </para>
8131
8132 <para>
8133 If any standby server's replay LSN stopped advancing,
8134 the <structfield>write_lag</structfield>
8135 and <structfield>flush_lag</structfield> columns would eventually
8136 stop updating.
8137 </para>
8138 </listitem>
8139
8140 <listitem>
8141 <!--
8142 Author: Fujii Masao <[email protected]>
8143 Branch: master [f33e60a53] 2025-10-22 20:09:43 +0900
8144 Branch: REL_18_STABLE [6ff7ba9fe] 2025-10-22 20:10:58 +0900
8145 Branch: REL_17_STABLE [1db2870bb] 2025-10-22 20:11:47 +0900
8146 Branch: REL_16_STABLE [4fd916eab] 2025-10-22 20:12:36 +0900
8147 Branch: REL_15_STABLE [caf529aba] 2025-10-22 20:13:15 +0900
8148 Branch: REL_14_STABLE [f106f53df] 2025-10-22 20:14:02 +0900
8149 Branch: REL_13_STABLE [b00a16bae] 2025-10-22 20:14:07 +0900
8150 -->
8151 <para>
8152 Avoid duplicative log messages about
8153 invalid <varname>primary_slot_name</varname> settings (Fujii Masao)
8154 <ulink url="&commit_baseurl;6ff7ba9fe">&sect;</ulink>
8155 </para>
8156 </listitem>
8157
8158 <listitem>
8159 <!--
8160 Author: Amit Kapila <[email protected]>
8161 Branch: master [e0dc4bbfb] 2025-10-27 06:48:32 +0000
8162 Branch: REL_18_STABLE [b45a8d7d8] 2025-10-27 06:37:35 +0000
8163 Branch: REL_17_STABLE [0024f5a10] 2025-10-27 06:34:29 +0000
8164 -->
8165 <para>
8166 Avoid failures when <varname>synchronized_standby_slots</varname>
8167 references nonexistent replication slots (Shlok Kyal)
8168 <ulink url="&commit_baseurl;b45a8d7d8">&sect;</ulink>
8169 </para>
8170 </listitem>
8171
8172 <listitem>
8173 <!--
8174 Author: Michael Paquier <[email protected]>
8175 Branch: master [912af1c7e] 2025-10-10 09:23:59 +0900
8176 Branch: REL_18_STABLE [9a6ea00ac] 2025-10-10 09:24:48 +0900
8177 Branch: REL_17_STABLE [42348839d] 2025-10-10 09:24:50 +0900
8178 Branch: REL_16_STABLE [bfdd1a12d] 2025-10-10 09:24:53 +0900
8179 Branch: REL_15_STABLE [0adf424b4] 2025-10-10 09:24:54 +0900
8180 Branch: REL_14_STABLE [f57f2760e] 2025-10-10 09:24:57 +0900
8181 Branch: REL_13_STABLE [c878d9808] 2025-10-10 09:24:59 +0900
8182 -->
8183 <para>
8184 Remove the unfinished slot state file after failing to write a
8185 replication slot's state to disk (Michael Paquier)
8186 <ulink url="&commit_baseurl;9a6ea00ac">&sect;</ulink>
8187 </para>
8188
8189 <para>
8190 Previously, a failure such as out-of-disk-space resulted in leaving
8191 a temporary <filename>state.tmp</filename> file behind. That's
8192 problematic because it would block all subsequent attempts to
8193 write the state, requiring manual intervention to clean up.
8194 </para>
8195 </listitem>
8196
8197 <listitem>
8198 <!--
8199 Author: Amit Kapila <[email protected]>
8200 Branch: master [e41d954da] 2025-09-24 04:11:53 +0000
8201 Branch: REL_18_STABLE [37fc5de43] 2025-09-24 04:00:15 +0000
8202 Branch: REL_17_STABLE [2f6e1a490] 2025-09-24 03:49:02 +0000
8203 Branch: REL_16_STABLE [a54c7a113] 2025-09-24 03:38:27 +0000
8204 -->
8205 <para>
8206 Fix mishandling of lock timeout signals in parallel apply workers
8207 for logical replication (Hayato Kuroda)
8208 <ulink url="&commit_baseurl;37fc5de43">&sect;</ulink>
8209 </para>
8210
8211 <para>
8212 The same signal number was being used for both worker shutdown and
8213 lock timeout, leading to confusion.
8214 </para>
8215 </listitem>
8216
8217 <listitem>
8218 <!--
8219 Author: Michael Paquier <[email protected]>
8220 Branch: master [17b2d5ec7] 2025-11-04 10:47:38 +0900
8221 Branch: REL_18_STABLE [a14201073] 2025-11-04 10:52:33 +0900
8222 Branch: REL_17_STABLE [e7340b484] 2025-11-04 10:52:35 +0900
8223 Branch: REL_16_STABLE [9b6109607] 2025-11-04 10:52:38 +0900
8224 Branch: REL_15_STABLE [da5ea6c70] 2025-11-04 10:52:41 +0900
8225 Branch: REL_14_STABLE [a1b8b3b2e] 2025-11-04 10:52:42 +0900
8226 Branch: REL_13_STABLE [25b484080] 2025-11-04 10:52:44 +0900
8227 -->
8228 <para>
8229 Avoid unwanted WAL receiver shutdown when switching from streaming
8230 to archive WAL source (Xuneng Zhou)
8231 <ulink url="&commit_baseurl;a14201073">&sect;</ulink>
8232 </para>
8233
8234 <para>
8235 During a timeline change, a standby server's WAL receiver should
8236 remain alive, waiting for a new WAL streaming start point. Instead
8237 it was repeatedly shutting down and immediately getting restarted,
8238 which could confuse status monitoring code.
8239 </para>
8240 </listitem>
8241
8242 <listitem>
8243 <!--
8244 Author: Masahiko Sawada <[email protected]>
8245 Branch: master [b46efe904] 2025-10-09 10:59:27 -0700
8246 Branch: REL_18_STABLE [32b95fc71] 2025-10-09 10:59:29 -0700
8247 Branch: REL_17_STABLE [a61592253] 2025-10-09 10:59:31 -0700
8248 Branch: REL_16_STABLE [b07682bce] 2025-10-09 10:59:34 -0700
8249 Branch: REL_15_STABLE [c40761759] 2025-10-09 10:59:36 -0700
8250 -->
8251 <para>
8252 Fix use-after-free issue in the relation synchronization cache
8253 maintained by the <application>pgoutput</application> logical
8254 decoding plugin (Vignesh C, Masahiko Sawada)
8255 <ulink url="&commit_baseurl;32b95fc71">&sect;</ulink>
8256 </para>
8257
8258 <para>
8259 An error during logical decoding could result in crashes in
8260 subsequent logical decoding attempts in the same session.
8261 The case is only reachable when <application>pgoutput</application>
8262 is invoked via SQL functions.
8263 </para>
8264 </listitem>
8265
8266 <listitem>
8267 <!--
8268 Author: Michael Paquier <[email protected]>
8269 Branch: master [d43209468] 2025-10-30 13:13:28 +0900
8270 Branch: REL_18_STABLE [bf3dba508] 2025-10-30 13:13:31 +0900
8271 Branch: REL_17_STABLE [f3fb6bc9f] 2025-10-30 13:13:34 +0900
8272 Branch: REL_16_STABLE [e3714dc05] 2025-10-30 13:13:37 +0900
8273 -->
8274 <para>
8275 Avoid unnecessary invalidation of logical replication slots
8276 (Bertrand Drouvot)
8277 <ulink url="&commit_baseurl;bf3dba508">&sect;</ulink>
8278 </para>
8279 </listitem>
8280
8281 <listitem>
8282 <!--
8283 Author: Jeff Davis <[email protected]>
8284 Branch: master [d115de9d8] 2025-11-04 16:48:16 -0800
8285 Branch: REL_18_STABLE [3ebea75f9] 2025-11-04 16:49:00 -0800
8286 -->
8287 <para>
8288 Re-establish special case for <literal>C</literal> collation in
8289 locale setup (Jeff Davis)
8290 <ulink url="&commit_baseurl;3ebea75f9">&sect;</ulink>
8291 </para>
8292
8293 <para>
8294 This fixes a regression in access to shared catalogs early in
8295 backend startup, before a database has been selected. It is not
8296 known to be a problem for any
8297 core <productname>PostgreSQL</productname> code, but some extensions
8298 were broken.
8299 </para>
8300 </listitem>
8301
8302 <listitem>
8303 <!--
8304 Author: Tom Lane <[email protected]>
8305 Branch: master [03bf7a12c] 2025-10-13 17:56:45 -0400
8306 Branch: REL_18_STABLE [b48ae226e] 2025-10-13 17:56:45 -0400
8307 Branch: REL_17_STABLE [4c53519e1] 2025-10-13 17:56:45 -0400
8308 Branch: REL_16_STABLE [9883e3cd1] 2025-10-13 17:56:45 -0400
8309 Branch: REL_15_STABLE [f91666c83] 2025-10-13 17:56:45 -0400
8310 Branch: REL_14_STABLE [e91eb4ad6] 2025-10-13 17:56:45 -0400
8311 Branch: REL_13_STABLE [75a555d61] 2025-10-13 17:56:45 -0400
8312 -->
8313 <para>
8314 Fix incorrect printing of messages about failures in checking
8315 whether the user has Windows administrator privilege (Bryan Green)
8316 <ulink url="&commit_baseurl;b48ae226e">&sect;</ulink>
8317 </para>
8318
8319 <para>
8320 This code would have crashed or at least printed garbage.
8321 No such cases have been reported though, indicating that failure of
8322 these system calls is extremely rare.
8323 </para>
8324 </listitem>
8325
8326 <listitem>
8327 <!--
8328 Author: Tom Lane <[email protected]>
8329 Branch: master [d4baa327a] 2025-11-05 11:09:45 -0500
8330 Branch: REL_18_STABLE [6d8acb777] 2025-11-05 11:09:30 -0500
8331 Branch: REL_17_STABLE [a9515f294] 2025-11-05 11:09:30 -0500
8332 Branch: REL_16_STABLE [c775bf048] 2025-11-05 11:09:30 -0500
8333 -->
8334 <para>
8335 Avoid crash when attempting to
8336 test <productname>PostgreSQL</productname> with certain libsanitizer
8337 options (Emmanuel Sibi, Jacob Champion)
8338 <ulink url="&commit_baseurl;6d8acb777">&sect;</ulink>
8339 </para>
8340 </listitem>
8341
8342 <listitem>
8343 <!--
8344 Author: David Rowley <[email protected]>
8345 Branch: master [50eb4e118] 2025-10-30 14:48:10 +1300
8346 Branch: REL_18_STABLE [af3a79e08] 2025-10-30 14:49:07 +1300
8347 Branch: REL_17_STABLE [bd6f986c9] 2025-10-30 14:49:42 +1300
8348 Branch: REL_16_STABLE [cdc04a6c3] 2025-10-30 14:50:05 +1300
8349 Branch: REL_15_STABLE [f3420e006] 2025-10-30 14:50:26 +1300
8350 Branch: REL_14_STABLE [86bd9497f] 2025-10-30 14:50:46 +1300
8351 Branch: REL_13_STABLE [7b955c227] 2025-10-30 14:51:08 +1300
8352 -->
8353 <para>
8354 Fix false memory-context-checking warnings in debug builds
8355 on 64-bit Windows (David Rowley)
8356 <ulink url="&commit_baseurl;af3a79e08">&sect;</ulink>
8357 </para>
8358 </listitem>
8359
8360 <listitem>
8361 <!--
8362 Author: Tom Lane <[email protected]>
8363 Branch: master [7504d2be9] 2025-09-27 14:29:41 -0400
8364 Branch: REL_18_STABLE [78a284b0b] 2025-09-27 14:29:41 -0400
8365 Branch: REL_17_STABLE [3fc9aa5b0] 2025-09-27 14:29:41 -0400
8366 Branch: REL_16_STABLE [b7f6798c0] 2025-09-27 14:29:41 -0400
8367 Branch: REL_15_STABLE [9ca79896a] 2025-09-27 14:29:41 -0400
8368 Branch: REL_14_STABLE [0be39b4b1] 2025-09-27 14:29:41 -0400
8369 -->
8370 <para>
8371 Correctly handle <literal>GROUP BY DISTINCT</literal> in PL/pgSQL
8372 assignment statements (Tom Lane)
8373 <ulink url="&commit_baseurl;78a284b0b">&sect;</ulink>
8374 </para>
8375
8376 <para>
8377 The parser failed to record the <literal>DISTINCT</literal> option
8378 in this context, so that the command would act as if it were
8379 plain <literal>GROUP BY</literal>.
8380 </para>
8381 </listitem>
8382
8383 <listitem>
8384 <!--
8385 Author: Tom Lane <[email protected]>
8386 Branch: master [798b19d27] 2025-10-23 11:47:46 -0400
8387 Branch: REL_18_STABLE [447a794f6] 2025-10-23 11:47:46 -0400
8388 Branch: REL_17_STABLE [fbc41a145] 2025-10-23 11:47:46 -0400
8389 Branch: REL_16_STABLE [cbfd4d0f8] 2025-10-23 11:47:46 -0400
8390 Branch: REL_15_STABLE [4cde73259] 2025-10-23 11:47:46 -0400
8391 Branch: REL_14_STABLE [7fb8c9240] 2025-10-23 11:47:46 -0400
8392 Branch: REL_13_STABLE [d90c92d1c] 2025-10-23 11:47:46 -0400
8393 -->
8394 <para>
8395 Avoid leaking memory when handling a SQL error within PL/Python
8396 (Tom Lane)
8397 <ulink url="&commit_baseurl;447a794f6">&sect;</ulink>
8398 </para>
8399
8400 <para>
8401 This fixes a session-lifespan memory leak introduced in our previous
8402 minor releases.
8403 </para>
8404 </listitem>
8405
8406 <listitem>
8407 <!--
8408 Author: Tom Lane <[email protected]>
8409 Branch: master [ea78bd6d5] 2025-10-05 16:27:47 -0400
8410 Branch: REL_18_STABLE [d83879a32] 2025-10-05 16:27:47 -0400
8411 Branch: REL_17_STABLE [1c4671f7b] 2025-10-05 16:27:47 -0400
8412 Branch: REL_16_STABLE [46c4478db] 2025-10-05 16:27:47 -0400
8413 Branch: REL_15_STABLE [771b106d1] 2025-10-05 16:27:47 -0400
8414 Branch: REL_14_STABLE [f46d77377] 2025-10-05 16:27:47 -0400
8415 Branch: REL_13_STABLE [fc287cf3c] 2025-10-05 16:27:47 -0400
8416 -->
8417 <para>
8418 Fix <application>libpq</application>'s handling of socket-related
8419 errors on Windows within its GSSAPI logic (Ning Wu, Tom Lane)
8420 <ulink url="&commit_baseurl;d83879a32">&sect;</ulink>
8421 </para>
8422
8423 <para>
8424 The code for encrypting/decrypting transmitted data using GSSAPI did
8425 not correctly recognize error conditions on the connection socket,
8426 since Windows reports those differently than other platforms. This
8427 led to failure to make such connections on Windows.
8428 </para>
8429 </listitem>
8430
8431 <listitem>
8432 <!--
8433 Author: Álvaro Herrera <[email protected]>
8434 Branch: master [615ff828e] 2025-10-18 18:18:19 +0200
8435 Branch: REL_18_STABLE [0fe07fa11] 2025-10-18 18:18:19 +0200
8436 Branch: REL_17_STABLE [c945b06d5] 2025-10-18 18:18:19 +0200
8437 -->
8438 <para>
8439 Fix dumping of non-inherited not-null constraints on inherited table
8440 columns (Dilip Kumar)
8441 <ulink url="&commit_baseurl;0fe07fa11">&sect;</ulink>
8442 </para>
8443
8444 <para>
8445 <application>pg_dump</application> failed to preserve such
8446 constraints when dumping from a pre-v18 server.
8447 </para>
8448 </listitem>
8449
8450 <listitem>
8451 <!--
8452 Author: Álvaro Herrera <[email protected]>
8453 Branch: master [4921a5972] 2025-10-18 17:50:10 +0200
8454 Branch: REL_18_STABLE [162e70ea0] 2025-10-18 17:50:10 +0200
8455 Branch: REL_17_STABLE [7419c99a2] 2025-10-18 17:50:10 +0200
8456 Branch: REL_16_STABLE [06c1ee6b7] 2025-10-18 17:50:10 +0200
8457 Branch: REL_15_STABLE [4cc3b4445] 2025-10-18 17:50:10 +0200
8458 Branch: REL_14_STABLE [6062c3db3] 2025-10-18 17:50:10 +0200
8459 Branch: REL_13_STABLE [d20df9590] 2025-10-18 17:50:10 +0200
8460 -->
8461 <para>
8462 Fix <application>pg_dump</application>'s sorting of
8463 foreign key constraints (Álvaro Herrera)
8464 <ulink url="&commit_baseurl;162e70ea0">&sect;</ulink>
8465 </para>
8466
8467 <para>
8468 Ensure consistent ordering of these database objects, as was
8469 already done for other object types.
8470 </para>
8471 </listitem>
8472
8473 <listitem>
8474 <!--
8475 Author: Daniel Gustafsson <[email protected]>
8476 Branch: master [e686010c5] 2025-08-29 19:28:46 +0200
8477 Branch: REL_18_STABLE Release: REL_18_0 [8980c724b] 2025-08-29 19:28:46 +0200
8478 Branch: REL_17_STABLE [92268b35d] 2025-08-29 19:28:46 +0200
8479 Branch: REL_16_STABLE [ec017a305] 2025-08-29 19:28:46 +0200
8480 Author: Tom Lane <[email protected]>
8481 Branch: master [a239c4a0c] 2025-10-13 12:44:20 -0400
8482 Branch: REL_18_STABLE [6a4009747] 2025-10-13 12:44:20 -0400
8483 Branch: REL_17_STABLE [bf18e9bd7] 2025-10-13 12:44:20 -0400
8484 Branch: REL_16_STABLE [1518b7d76] 2025-10-13 12:44:20 -0400
8485 Branch: master [277dec651] 2025-10-19 14:36:58 -0400
8486 Branch: REL_18_STABLE [aa1fcd087] 2025-10-19 14:36:58 -0400
8487 Branch: REL_17_STABLE [2efca1633] 2025-10-19 14:36:58 -0400
8488 Branch: REL_16_STABLE [c865f5b9f] 2025-10-19 14:36:58 -0400
8489 Branch: REL_15_STABLE [8b9924bce] 2025-10-19 14:36:58 -0400
8490 Branch: REL_14_STABLE [40dc710a6] 2025-10-19 14:36:58 -0400
8491 Branch: REL_13_STABLE [33276cd02] 2025-10-19 14:36:58 -0400
8492 -->
8493 <para>
8494 Fix assorted errors in the data compression logic
8495 in <application>pg_dump</application>
8496 and <application>pg_restore</application>
8497 (Daniel Gustafsson, Tom Lane)
8498 <ulink url="&commit_baseurl;8980c724b">&sect;</ulink>
8499 <ulink url="&commit_baseurl;6a4009747">&sect;</ulink>
8500 <ulink url="&commit_baseurl;aa1fcd087">&sect;</ulink>
8501 </para>
8502
8503 <para>
8504 Error checking was missing or incorrect in several places, and there
8505 were also portability issues that would manifest on big-endian
8506 hardware. These problems had been missed because this code is only
8507 used to read compressed TOC files within directory-format
8508 dumps. <application>pg_dump</application> never produces such a
8509 dump; the case can be reached only by manually compressing the TOC
8510 file after the fact, which is a supported thing to do but very
8511 uncommon.
8512 </para>
8513 </listitem>
8514
8515 <listitem>
8516 <!--
8517 Author: Michael Paquier <[email protected]>
8518 Branch: master [902c08887] 2025-10-03 14:03:55 +0900
8519 Branch: REL_18_STABLE [c00637b5f] 2025-10-03 14:04:00 +0900
8520 Branch: REL_17_STABLE [de6de069d] 2025-10-03 14:04:01 +0900
8521 Branch: REL_16_STABLE [640590bb4] 2025-10-03 14:04:03 +0900
8522 Branch: REL_15_STABLE [b5cefc197] 2025-10-03 14:04:05 +0900
8523 Branch: REL_14_STABLE [9b3beb7c6] 2025-10-03 14:04:06 +0900
8524 Branch: REL_13_STABLE [f1a2f3a0c] 2025-10-03 14:04:08 +0900
8525 -->
8526 <para>
8527 Fix <application>pgbench</application> to error out cleanly if
8528 a <literal>COPY</literal> operation is started (Anthonin Bonnefoy)
8529 <ulink url="&commit_baseurl;c00637b5f">&sect;</ulink>
8530 </para>
8531
8532 <para>
8533 <application>pgbench</application> doesn't intend to support this
8534 case, but previously it went into an infinite loop.
8535 </para>
8536 </listitem>
8537
8538 <listitem>
8539 <!--
8540 Author: Fujii Masao <[email protected]>
8541 Branch: master [19d4f9ffc] 2025-09-30 23:52:28 +0900
8542 Branch: REL_18_STABLE [29aabbc43] 2025-09-30 23:53:32 +0900
8543 Branch: REL_17_STABLE [a912118c6] 2025-09-30 23:53:46 +0900
8544 Branch: REL_16_STABLE [36c4d30c8] 2025-09-30 23:53:53 +0900
8545 Branch: REL_15_STABLE [bdccb6302] 2025-09-30 23:54:01 +0900
8546 Branch: REL_14_STABLE [cb21e1f92] 2025-09-30 23:55:02 +0900
8547 Branch: REL_13_STABLE [7d7e81d1e] 2025-09-30 23:55:33 +0900
8548 -->
8549 <para>
8550 Fix <application>pgbench</application>'s reporting of multiple
8551 errors (Yugo Nagata)
8552 <ulink url="&commit_baseurl;29aabbc43">&sect;</ulink>
8553 </para>
8554
8555 <para>
8556 In cases where two successive <function>PQgetResult</function> calls
8557 both fail, <application>pgbench</application> might report the wrong
8558 error message.
8559 </para>
8560 </listitem>
8561
8562 <listitem>
8563 <!--
8564 Author: Fujii Masao <[email protected]>
8565 Branch: master [8bb174295] 2025-09-26 21:23:43 +0900
8566 Branch: REL_18_STABLE [c736808e0] 2025-09-26 21:24:59 +0900
8567 Branch: REL_17_STABLE [f39d9164b] 2025-09-26 21:25:05 +0900
8568 Branch: REL_16_STABLE [8b2e290bd] 2025-09-26 21:25:11 +0900
8569 Branch: REL_15_STABLE [704f51771] 2025-09-26 21:25:17 +0900
8570 -->
8571 <para>
8572 In <application>pgbench</application>, fix faulty assertion about
8573 errors in pipeline mode (Yugo Nagata)
8574 <ulink url="&commit_baseurl;c736808e0">&sect;</ulink>
8575 </para>
8576 </listitem>
8577
8578 <listitem>
8579 <!--
8580 Author: Tom Lane <[email protected]>
8581 Branch: master [9224c3025] 2025-10-22 13:38:40 -0400
8582 Branch: REL_18_STABLE [e2072b47b] 2025-10-22 13:38:37 -0400
8583 Branch: REL_17_STABLE [4eb6992af] 2025-10-22 13:38:37 -0400
8584 -->
8585 <para>
8586 Fix per-file memory leakage
8587 in <application>pg_combinebackup</application> (Tom Lane)
8588 <ulink url="&commit_baseurl;e2072b47b">&sect;</ulink>
8589 </para>
8590 </listitem>
8591
8592 <listitem>
8593 <!--
8594 Author: Masahiko Sawada <[email protected]>
8595 Branch: master [8ae0f6a0c] 2025-11-04 15:47:25 -0800
8596 Branch: REL_18_STABLE [71aa2e114] 2025-11-04 15:47:22 -0800
8597 Branch: master [eab9e4e27] 2025-08-19 12:11:42 -0700
8598 Branch: REL_18_STABLE Release: REL_18_0 [0beb7e933] 2025-08-19 12:11:39 -0700
8599 Branch: REL_17_STABLE [b6090ed96] 2025-08-19 12:11:37 -0700
8600 Branch: REL_16_STABLE [815fcfb20] 2025-08-19 12:11:34 -0700
8601 Branch: REL_15_STABLE [eb9ee4d18] 2025-08-19 12:11:32 -0700
8602 Branch: REL_14_STABLE [79643105a] 2025-08-19 12:11:29 -0700
8603 Branch: REL_13_STABLE [7d8d36289] 2025-08-19 12:11:25 -0700
8604 -->
8605 <para>
8606 Ensure that <filename>contrib/pg_buffercache</filename> functions
8607 can be canceled (Satyanarayana Narlapuram, Yuhang Qiu)
8608 <ulink url="&commit_baseurl;71aa2e114">&sect;</ulink>
8609 <ulink url="&commit_baseurl;0beb7e933">&sect;</ulink>
8610 </para>
8611
8612 <para>
8613 Some code paths were capable of running for a long time without
8614 checking for interrupts.
8615 </para>
8616 </listitem>
8617
8618 <listitem>
8619 <!--
8620 Author: Nathan Bossart <[email protected]>
8621 Branch: master [208927e65] 2025-10-17 11:36:50 -0500
8622 Branch: REL_18_STABLE [3ccf8e9ac] 2025-10-17 11:36:50 -0500
8623 Branch: REL_17_STABLE [a0551bc57] 2025-10-17 11:36:50 -0500
8624 Branch: REL_16_STABLE [fae0ce5e3] 2025-10-17 11:36:50 -0500
8625 Branch: REL_15_STABLE [6c03ae8d6] 2025-10-17 11:36:50 -0500
8626 Branch: REL_14_STABLE [f146eb45c] 2025-10-17 11:36:50 -0500
8627 Branch: REL_13_STABLE [19a64f567] 2025-10-17 11:36:50 -0500
8628 Author: Tom Lane <[email protected]>
8629 Branch: master [da44d71e7] 2025-10-18 18:36:21 -0400
8630 Branch: REL_18_STABLE [c29d32d27] 2025-10-18 18:36:21 -0400
8631 Branch: REL_17_STABLE [d4e8c37cc] 2025-10-18 18:36:21 -0400
8632 Branch: REL_16_STABLE [c26a8eaf6] 2025-10-18 18:36:21 -0400
8633 -->
8634 <para>
8635 Fix <filename>contrib/pg_prewarm</filename>'s privilege checks for
8636 indexes (Ayush Vatsa, Nathan Bossart)
8637 <ulink url="&commit_baseurl;3ccf8e9ac">&sect;</ulink>
8638 <ulink url="&commit_baseurl;c29d32d27">&sect;</ulink>
8639 </para>
8640
8641 <para>
8642 <function>pg_prewarm()</function> requires <literal>SELECT</literal>
8643 privilege on relations to be prewarmed. However, since indexes have
8644 no SQL privileges of their own, this resulted in non-superusers
8645 being unable to prewarm indexes. Instead, check
8646 for <literal>SELECT</literal> privilege on the index's table.
8647 </para>
8648 </listitem>
8649
8650 <listitem>
8651 <!--
8652 Author: Álvaro Herrera <[email protected]>
8653 Branch: master [16edc1b94] 2025-10-29 12:35:02 +0100
8654 Branch: REL_18_STABLE [b1635c166] 2025-10-29 12:35:02 +0100
8655 -->
8656 <para>
8657 In <filename>contrib/pg_stat_statements</filename>, avoid
8658 crash when two or more constants are marked as having the same
8659 location in the SQL statement text (Sami Imseih, Dmitry Dolgov)
8660 <ulink url="&commit_baseurl;b1635c166">&sect;</ulink>
8661 </para>
8662 </listitem>
8663
8664 <listitem>
8665 <!--
8666 Author: Michael Paquier <[email protected]>
8667 Branch: master [684a745f5] 2025-10-02 11:07:30 +0900
8668 Branch: REL_18_STABLE [fc295beb7] 2025-10-02 11:09:10 +0900
8669 Branch: REL_17_STABLE [036decbba] 2025-10-02 11:09:12 +0900
8670 Branch: REL_16_STABLE [c0f9fe877] 2025-10-02 11:09:13 +0900
8671 Branch: REL_15_STABLE [49b5f0b53] 2025-10-02 11:09:15 +0900
8672 Branch: REL_14_STABLE [ee2dbcad0] 2025-10-02 11:09:17 +0900
8673 Branch: REL_13_STABLE [c207bf473] 2025-10-02 11:09:19 +0900
8674 -->
8675 <para>
8676 Make <filename>contrib/pgstattuple</filename> more robust about
8677 empty or invalid index pages (Nitin Motiani)
8678 <ulink url="&commit_baseurl;fc295beb7">&sect;</ulink>
8679 </para>
8680
8681 <para>
8682 Count all-zero pages as free space, and ignore pages that are
8683 invalid according to a check of the page's special-space size.
8684 The code for btree indexes already counted all-zero pages as free,
8685 but the hash and gist code would error out, which has been found to
8686 be much less user-friendly. Similarly, make all three cases agree
8687 on ignoring corrupted pages rather than throwing errors.
8688 </para>
8689 </listitem>
8690
8691 <listitem>
8692 <!--
8693 Author: Thomas Munro <[email protected]>
8694 Branch: master [c5d34f4a5] 2025-11-08 12:26:43 +1300
8695 Branch: REL_18_STABLE [f8ccab0e9] 2025-11-08 12:28:15 +1300
8696 Branch: REL_17_STABLE [03d9140cb] 2025-11-08 12:28:52 +1300
8697 Branch: REL_16_STABLE [2f76ffe5e] 2025-11-08 12:29:15 +1300
8698 Branch: REL_15_STABLE [1c7cba4c5] 2025-11-08 12:30:08 +1300
8699 Branch: REL_14_STABLE [d8ba910b0] 2025-11-08 12:32:42 +1300
8700 Branch: REL_13_STABLE [77b5b2c6f] 2025-11-08 12:33:01 +1300
8701 -->
8702 <para>
8703 Harden our read and write barrier macros to satisfy Clang
8704 (Thomas Munro)
8705 <ulink url="&commit_baseurl;f8ccab0e9">&sect;</ulink>
8706 </para>
8707
8708 <para>
8709 We supposed that <function>__atomic_thread_fence()</function> is a
8710 sufficient barrier to prevent the C compiler from re-ordering memory
8711 accesses around it, but it appears that that's not true for Clang,
8712 allowing it to generate incorrect code for at least RISC-V, MIPS,
8713 and LoongArch machines. Add explicit compiler barriers to fix that.
8714 </para>
8715 </listitem>
8716
8717 <listitem>
8718 <!--
8719 Author: Álvaro Herrera <[email protected]>
8720 Branch: master [6ad9378c9] 2025-10-16 20:21:05 +0200
8721 Branch: REL_18_STABLE [6aa04a60c] 2025-10-16 20:21:05 +0200
8722 Branch: REL_17_STABLE [a8933194e] 2025-10-16 20:21:05 +0200
8723 Branch: REL_16_STABLE [a506b0c0a] 2025-10-16 20:21:05 +0200
8724 Branch: REL_15_STABLE [33202cba8] 2025-10-16 20:21:05 +0200
8725 Branch: REL_14_STABLE [56cd332f8] 2025-10-16 20:21:05 +0200
8726 Branch: REL_13_STABLE [f768f5a7d] 2025-10-16 20:21:05 +0200
8727 -->
8728 <para>
8729 Fix PGXS build infrastructure to support building
8730 NLS <filename>po</filename> files for extensions (Ryo Matsumura)
8731 <ulink url="&commit_baseurl;6aa04a60c">&sect;</ulink>
8732 </para>
8733 </listitem>
8734
8735 </itemizedlist>
8736
8737 </sect2>
8738 </sect1>
8739
8740 <sect1 id="release-18">
8741 <title>Release 18</title>
8742
8743 <formalpara>
8744 <title>Release date:</title>
8745 <para>2025-09-25</para>
8746 </formalpara>
8747
8748 <sect2 id="release-18-highlights">
8749 <title>Overview</title>
8750
8751 <para>
8752 <productname>PostgreSQL</productname> 18 contains many new features
8753 and enhancements, including:
8754 </para>
8755
8756 <itemizedlist>
8757
8758 <listitem>
8759 <para>
8760 An asynchronous I/O (AIO) subsystem that can improve performance of
8761 sequential scans, bitmap heap scans, vacuums, and other operations.
8762 </para>
8763 </listitem>
8764
8765 <listitem>
8766 <para>
8767 <link linkend="pgupgrade"><application>pg_upgrade</application></link>
8768 now retains optimizer statistics.
8769 </para>
8770 </listitem>
8771
8772 <listitem>
8773 <para>
8774 Support for "skip scan" lookups that allow using
8775 <link linkend="indexes-multicolumn">multicolumn B-tree indexes</link> in
8776 more cases.
8777 </para>
8778 </listitem>
8779
8780 <listitem>
8781 <para>
8782 <link linkend="func_uuid_gen_table"><function>uuidv7()</function></link>
8783 function for generating timestamp-ordered
8784 <link linkend="datatype-uuid">UUIDs</link>.
8785 </para>
8786 </listitem>
8787
8788 <listitem>
8789 <para>
8790 Virtual
8791 <link linkend="sql-createtable-parms-generated-stored">generated columns</link>
8792 that compute their values during read operations. This is now the
8793 default for generated columns.
8794 </para>
8795 </listitem>
8796
8797 <listitem>
8798 <para>
8799 <link linkend="auth-oauth">OAuth authentication</link> support.
8800 </para>
8801 </listitem>
8802
8803 <listitem>
8804 <para>
8805 <literal>OLD</literal> and <literal>NEW</literal> support for
8806 <link linkend="dml-returning"><literal>RETURNING</literal></link> clauses
8807 in <xref linkend="sql-insert"/>, <xref linkend="sql-update"/>,
8808 <xref linkend="sql-delete"/>, and <xref linkend="sql-merge"/> commands.
8809 </para>
8810 </listitem>
8811
8812 <listitem>
8813 <para>
8814 Temporal constraints, or constraints over ranges, for
8815 <link linkend="sql-createtable-parms-primary-key">PRIMARY KEY</link>,
8816 <link linkend="sql-createtable-parms-unique">UNIQUE</link>, and
8817 <link linkend="sql-createtable-parms-references">FOREIGN KEY</link>
8818 constraints.
8819 </para>
8820 </listitem>
8821 </itemizedlist>
8822
8823 <para>
8824 The above items and other new features of
8825 <productname>PostgreSQL</productname> 18 are explained in more detail
8826 in the sections below.
8827 </para>
8828
8829 </sect2>
8830
8831 <sect2 id="release-18-migration">
8832
8833 <title>Migration to Version 18</title>
8834
8835 <para>
8836 A dump/restore using <xref linkend="app-pg-dumpall"/> or use of
8837 <xref linkend="pgupgrade"/> or logical replication is required for
8838 those wishing to migrate data from any previous release. See <xref
8839 linkend="upgrading"/> for general information on migrating to new
8840 major releases.
8841 </para>
8842
8843 <para>
8844 Version 18 contains a number of changes that may affect compatibility
8845 with previous releases. Observe the following incompatibilities:
8846 </para>
8847
8848 <itemizedlist>
8849
8850 <!--
8851 Author: Peter Eisentraut <[email protected]>
8852 2024-10-16 [04bec894a04] initdb: Change default to using data checksums.
8853 -->
8854
8855 <listitem>
8856 <para>
8857 Change <xref linkend="app-initdb"/> default to enable data checksums
8858 (Greg Sabino Mullane)
8859 <ulink url="&commit_baseurl;04bec894a04">&sect;</ulink>
8860 </para>
8861
8862 <para>
8863 Checksums can be disabled with the
8864 new <application>initdb</application> option
8865 <option>--no-data-checksums</option>. <xref linkend="pgupgrade"/>
8866 requires matching cluster checksum settings, so this new option can
8867 be useful to upgrade non-checksum old clusters.
8868 </para>
8869 </listitem>
8870
8871 <!--
8872 Author: Tom Lane <[email protected]>
8873 2025-01-16 [d7674c9fa] Seek zone abbreviations in the IANA data before timezone
8874 -->
8875
8876 <listitem>
8877 <para>
8878 Change time zone abbreviation handling (Tom Lane)
8879 <ulink url="&commit_baseurl;d7674c9fa">&sect;</ulink>
8880 </para>
8881
8882 <para>
8883 The system will now favor the current session's time
8884 zone abbreviations before checking the server variable
8885 <xref linkend="guc-timezone-abbreviations"/>. Previously
8886 <varname>timezone_abbreviations</varname> was checked first.
8887 </para>
8888 </listitem>
8889
8890 <!--
8891 Author: Nathan Bossart <[email protected]>
8892 2024-12-02 [db6a4a985] Deprecate MD5 passwords.
8893 -->
8894
8895 <listitem>
8896 <para>
8897 Deprecate <link linkend="auth-password">MD5 password</link>
8898 authentication (Nathan Bossart)
8899 <ulink url="&commit_baseurl;db6a4a985">&sect;</ulink>
8900 </para>
8901
8902 <para>
8903 Support for MD5 passwords will be removed in a future major
8904 version release. <xref linkend="sql-createrole"/> and <xref
8905 linkend="sql-alterrole"/> now emit deprecation warnings when
8906 setting MD5 passwords. These warnings can be disabled by setting
8907 the <xref linkend="guc-md5-password-warnings"/> parameter to
8908 <literal>off</literal>.
8909 </para>
8910 </listitem>
8911
8912 <!--
8913 Author: David Rowley <[email protected]>
8914 2024-09-24 [62ddf7ee9] Add ONLY support for VACUUM and ANALYZE
8915 -->
8916
8917 <listitem>
8918 <para>
8919 Change <xref linkend="sql-vacuum"/> and <xref linkend="sql-analyze"/>
8920 to process the inheritance children of a parent (Michael Harris)
8921 <ulink url="&commit_baseurl;62ddf7ee9">&sect;</ulink>
8922 </para>
8923
8924 <para>
8925 The previous behavior can be performed by using the new
8926 <literal>ONLY</literal> option.
8927 </para>
8928 </listitem>
8929
8930 <!--
8931 Author: Tom Lane <[email protected]>
8932 2024-09-30 [770233748] Do not treat \. as an EOF marker in CSV mode for COPY IN
8933 Author: Tom Lane <[email protected]>
8934 2024-10-01 [da8a4c166] Reject a copy EOF marker that has data ahead of it on th
8935 -->
8936
8937 <listitem>
8938 <para>
8939 Prevent <link linkend="sql-copy"><command>COPY FROM</command></link>
8940 from treating <literal>\.</literal> as an end-of-file marker when
8941 reading <acronym>CSV</acronym> files (Daniel Vérité, Tom Lane)
8942 <ulink url="&commit_baseurl;770233748">&sect;</ulink>
8943 <ulink url="&commit_baseurl;da8a4c166">&sect;</ulink>
8944 </para>
8945
8946 <para>
8947 <xref linkend="app-psql"/> will still treat
8948 <literal>\.</literal> as an end-of-file marker when reading
8949 <acronym>CSV</acronym> files from <literal>STDIN</literal>.
8950 Older <application>psql</application> clients connecting to
8951 <productname>PostgreSQL</productname> 18 servers might experience <link
8952 linkend="app-psql-meta-commands-copy"><literal>\copy</literal></link>
8953 problems. This release also enforces that <literal>\.</literal>
8954 must appear alone on a line.
8955 </para>
8956 </listitem>
8957
8958 <!--
8959 Author: Michael Paquier <[email protected]>
8960 2024-10-03 [e2bab2d79] Remove support for unlogged on partitioned tables
8961 -->
8962
8963 <listitem>
8964 <para>
8965 Disallow unlogged partitioned tables (Michael Paquier)
8966 <ulink url="&commit_baseurl;e2bab2d79">&sect;</ulink>
8967 </para>
8968
8969 <para>
8970 Previously <link linkend="sql-altertable"><command>ALTER TABLE SET
8971 [UN]LOGGED</command></link> did nothing, and the creation of an
8972 unlogged partitioned table did not cause its children to be unlogged.
8973 </para>
8974 </listitem>
8975
8976 <!--
8977 Author: Tom Lane <[email protected]>
8978 2025-01-23 [01463e1cc] Ensure that AFTER triggers run as the instigating user.
8979 -->
8980
8981 <listitem>
8982 <para>
8983 Execute <literal>AFTER</literal> <link
8984 linkend="triggers">triggers</link> as the role that was active when
8985 trigger events were queued (Laurenz Albe)
8986 <ulink url="&commit_baseurl;01463e1cc">&sect;</ulink>
8987 </para>
8988
8989 <para>
8990 Previously such triggers were run as the role that was active at
8991 trigger execution time (e.g., at <xref linkend="sql-commit"/>).
8992 This is significant for cases where the role is changed between queue
8993 time and transaction commit.
8994 </para>
8995 </listitem>
8996
8997 <!--
8998 Author: Fujii Masao <[email protected]>
8999 2024-09-12 [fefa76f70] Remove old RULE privilege completely.
9000 -->
9001
9002 <listitem>
9003 <para>
9004 Remove non-functional support for rule privileges in <xref
9005 linkend="sql-grant"/>/<xref linkend="sql-revoke"/> (Fujii Masao)
9006 <ulink url="&commit_baseurl;fefa76f70">&sect;</ulink>
9007 </para>
9008
9009 <para>
9010 These have been non-functional since
9011 <productname>PostgreSQL</productname> 8.2.
9012 </para>
9013 </listitem>
9014
9015 <!--
9016 Author: David Rowley <[email protected]>
9017 2024-08-12 [f0d112759] Remove "parent" column from pg_backend_memory_contexts
9018 -->
9019
9020 <listitem>
9021 <para>
9022 Remove column <link
9023 linkend="view-pg-backend-memory-contexts"><structname>pg_backend_memory_contexts</structname></link>.<structfield>parent</structfield>
9024 (Melih Mutlu)
9025 <ulink url="&commit_baseurl;f0d112759">&sect;</ulink>
9026 </para>
9027
9028 <para>
9029 This is no longer needed since
9030 <structname>pg_backend_memory_contexts</structname>.<structfield>path</structfield>
9031 was added.
9032 </para>
9033 </listitem>
9034
9035 <!--
9036 Author: David Rowley <[email protected]>
9037 2024-07-25 [32d3ed816] Add path column to pg_backend_memory_contexts view
9038 Author: David Rowley <[email protected]>
9039 2025-04-18 [d9e03864b] Make levels 1-based in
9040 pg_log_backend_memory_contexts()
9041 Author: Fujii Masao <[email protected]>
9042 2025-04-21 [706cbed35] doc: Fix memory context level in pg_log_backend_memory_c
9043 -->
9044
9045 <listitem>
9046 <para>
9047 Change
9048 <structname>pg_backend_memory_contexts</structname>.<structfield>level</structfield>
9049 and <link
9050 linkend="functions-admin-signal-table"><function>pg_log_backend_memory_contexts()</function></link>
9051 to be one-based (Melih Mutlu, Atsushi Torikoshi, David Rowley,
9052 Fujii Masao)
9053 <ulink url="&commit_baseurl;32d3ed816">&sect;</ulink>
9054 <ulink url="&commit_baseurl;d9e03864b">&sect;</ulink>
9055 <ulink url="&commit_baseurl;706cbed35">&sect;</ulink>
9056 </para>
9057
9058 <para>
9059 These were previously zero-based.
9060 </para>
9061 </listitem>
9062
9063 <!--
9064 Author: Peter Eisentraut <[email protected]>
9065 2024-12-17 [fb1a18810f0] Remove ts_locale.c's lowerstr()
9066 -->
9067
9068 <listitem>
9069 <para>
9070 Change <link linkend="textsearch">full text search</link> to use the
9071 default collation provider of the cluster to read configuration files
9072 and dictionaries, rather than always using libc (Peter Eisentraut)
9073 <ulink url="&commit_baseurl;fb1a18810f0">&sect;</ulink>
9074 </para>
9075
9076 <para>
9077 Clusters that default to non-libc collation providers (e.g., ICU,
9078 builtin) that behave differently than libc for characters processed
9079 by LC_CTYPE could observe changes in behavior of some full-text
9080 search functions, as well as the <xref linkend="pgtrgm"/> extension.
9081 When upgrading such clusters using <xref linkend="pgupgrade"/>, it
9082 is recommended to reindex all indexes related to full-text search
9083 and <application>pg_trgm</application> after the upgrade.
9084 </para>
9085 </listitem>
9086
9087 </itemizedlist>
9088
9089 </sect2>
9090
9091 <sect2 id="release-18-changes">
9092 <title>Changes</title>
9093
9094 <para>
9095 Below you will find a detailed account of the changes between
9096 <productname>PostgreSQL</productname> 18 and the previous major
9097 release.
9098 </para>
9099
9100 <sect3 id="release-18-server">
9101 <title>Server</title>
9102
9103 <sect4 id="release-18-optimizer">
9104 <title>Optimizer</title>
9105
9106 <itemizedlist>
9107
9108 <!--
9109 Author: Alexander Korotkov <[email protected]>
9110 2025-02-17 [fc069a3a6] Implement Self-Join Elimination
9111 -->
9112
9113 <listitem>
9114 <para>
9115 Automatically remove some unnecessary table self-joins (Andrey
9116 Lepikhov, Alexander Kuzmenkov, Alexander Korotkov, Alena Rybakina)
9117 <ulink url="&commit_baseurl;fc069a3a6">&sect;</ulink>
9118 </para>
9119
9120 <para>
9121 This optimization can be disabled using server variable <xref
9122 linkend="guc-enable-self-join-elimination"/>.
9123 </para>
9124 </listitem>
9125
9126 <!--
9127 Author: Alexander Korotkov <[email protected]>
9128 2025-04-04 [c0962a113] Convert 'x IN (VALUES ...)' to 'x = ANY ...' then approp
9129 -->
9130
9131 <listitem>
9132 <para>
9133 Convert some <link
9134 linkend="functions-comparisons-in-scalar"><literal>IN (VALUES
9135 ...)</literal></link> to <literal>x = ANY ...</literal> for better
9136 optimizer statistics (Alena Rybakina, Andrei Lepikhov)
9137 <ulink url="&commit_baseurl;c0962a113">&sect;</ulink>
9138 </para>
9139 </listitem>
9140
9141 <!--
9142 Author: Alexander Korotkov <[email protected]>
9143 2024-11-24 [ae4569161] Teach bitmap path generation about transforming OR-claus
9144 -->
9145
9146 <listitem>
9147 <para>
9148 Allow transforming <link
9149 linkend="functions-logical"><literal>OR</literal></link>-clauses
9150 to arrays for faster index processing (Alexander Korotkov, Andrey
9151 Lepikhov)
9152 <ulink url="&commit_baseurl;ae4569161">&sect;</ulink>
9153 </para>
9154 </listitem>
9155
9156 <!--
9157 Author: Tom Lane <[email protected]>
9158 2024-09-10 [52c707483] Use a hash table to de-duplicate column names in ruleuti
9159 Author: Tom Lane <[email protected]>
9160 2024-12-19 [276279295] Convert SetOp to read its inputs as outerPlan and innerP
9161 Author: Tom Lane <[email protected]>
9162 2024-12-19 [8d96f57d5] Improve planner's handling of SetOp plans.
9163 Author: David Rowley <[email protected]>
9164 2024-09-05 [908a96861] Optimize WindowAgg's use of tuplestores
9165 -->
9166
9167 <listitem>
9168 <para>
9169 Speed up the processing of <link
9170 linkend="sql-intersect"><literal>INTERSECT</literal></link>,
9171 <link linkend="sql-except"><literal>EXCEPT</literal></link>, <link
9172 linkend="tutorial-window">window aggregates</link>, and <link
9173 linkend="sql-createview">view column aliases</link> (Tom Lane,
9174 David Rowley)
9175 <ulink url="&commit_baseurl;52c707483">&sect;</ulink>
9176 <ulink url="&commit_baseurl;276279295">&sect;</ulink>
9177 <ulink url="&commit_baseurl;8d96f57d5">&sect;</ulink>
9178 <ulink url="&commit_baseurl;908a96861">&sect;</ulink>
9179 </para>
9180 </listitem>
9181
9182 <!--
9183 Author: Richard Guo <[email protected]>
9184 2024-11-26 [a8ccf4e93] Reordering DISTINCT keys to match input path's pathkeys
9185 -->
9186
9187 <listitem>
9188 <para>
9189 Allow the keys of <link linkend="sql-distinct"><command>SELECT
9190 DISTINCT</command></link> to be internally reordered to avoid sorting
9191 (Richard Guo)
9192 <ulink url="&commit_baseurl;a8ccf4e93">&sect;</ulink>
9193 </para>
9194
9195 <para>
9196 This optimization can be disabled using <xref
9197 linkend="guc-enable-distinct-reordering"/>.
9198 </para>
9199 </listitem>
9200
9201 <!--
9202 Author: David Rowley <[email protected]>
9203 2024-12-12 [bd10ec529] Detect redundant GROUP BY columns using UNIQUE indexes
9204 -->
9205
9206 <listitem>
9207 <para>
9208 Ignore <link linkend="sql-groupby"><literal>GROUP BY</literal></link>
9209 columns that are functionally dependent on other columns (Zhang
9210 Mingli, Jian He, David Rowley)
9211 <ulink url="&commit_baseurl;bd10ec529">&sect;</ulink>
9212 </para>
9213
9214 <para>
9215 If a <literal>GROUP BY</literal> clause includes all columns of
9216 a unique index, as well as other columns of the same table, those
9217 other columns are redundant and can be dropped from the grouping.
9218 This was already true for non-deferred primary keys.
9219 </para>
9220 </listitem>
9221
9222 <!--
9223 Author: Richard Guo <[email protected]>
9224 2024-10-09 [67a54b9e8] Allow pushdown of HAVING clauses with grouping sets
9225 Author: Richard Guo <[email protected]>
9226 2024-09-10 [247dea89f] Introduce an RTE for the grouping step
9227 Author: Richard Guo <[email protected]>
9228 2024-09-10 [f5050f795] Mark expressions nullable by grouping sets
9229 Author: Richard Guo <[email protected]>
9230 2025-03-13 [cc5d98525] Fix incorrect handling of subquery pullup
9231 -->
9232
9233 <listitem>
9234 <para>
9235 Allow some <link
9236 linkend="sql-having"><literal>HAVING</literal></link> clauses
9237 on <link linkend="queries-grouping-sets"><literal>GROUPING
9238 SETS</literal></link> to be pushed to <link
9239 linkend="sql-where"><literal>WHERE</literal></link> clauses
9240 (Richard Guo)
9241 <ulink url="&commit_baseurl;67a54b9e8">&sect;</ulink>
9242 <ulink url="&commit_baseurl;247dea89f">&sect;</ulink>
9243 <ulink url="&commit_baseurl;f5050f795">&sect;</ulink>
9244 <ulink url="&commit_baseurl;cc5d98525">&sect;</ulink>
9245 </para>
9246
9247 <para>
9248 This allows earlier row filtering. This release also fixes some
9249 <literal>GROUPING SETS</literal> queries that used to return
9250 incorrect results.
9251 </para>
9252 </listitem>
9253
9254 <!--
9255 Author: David Rowley <[email protected]>
9256 2024-07-09 [036bdcec9] Teach planner how to estimate rows for timestamp generat
9257 Author: Dean Rasheed <[email protected]>
9258 2024-12-02 [97173536e] Add a planner support function for numeric generate_seri
9259 -->
9260
9261 <listitem>
9262 <para>
9263 Improve row estimates for <link
9264 linkend="functions-srf-series"><function>generate_series()</function></link>
9265 using <link linkend="datatype-numeric"><type>numeric</type></link>
9266 and <link linkend="datatype-datetime"><type>timestamp</type></link>
9267 values (David Rowley, Song Jinzhou)
9268 <ulink url="&commit_baseurl;036bdcec9">&sect;</ulink>
9269 <ulink url="&commit_baseurl;97173536e">&sect;</ulink>
9270 </para>
9271 </listitem>
9272
9273 <!--
9274 Author: Richard Guo <[email protected]>
9275 2024-07-05 [aa86129e1] Support "Right Semi Join" plan shapes
9276 -->
9277
9278 <listitem>
9279 <para>
9280 Allow the optimizer to use <literal>Right Semi Join</literal> plans
9281 (Richard Guo)
9282 <ulink url="&commit_baseurl;aa86129e1">&sect;</ulink>
9283 </para>
9284
9285 <para>
9286 Semi-joins are used when needing to find if there is at least
9287 one match.
9288 </para>
9289 </listitem>
9290
9291 <!--
9292 Author: Richard Guo <[email protected]>
9293 2024-10-09 [828e94c9d] Consider explicit incremental sort for mergejoins
9294 -->
9295
9296 <listitem>
9297 <para>
9298 Allow merge joins to use <link
9299 linkend="guc-enable-incremental-sort">incremental sorts</link>
9300 (Richard Guo)
9301 <ulink url="&commit_baseurl;828e94c9d">&sect;</ulink>
9302 </para>
9303 </listitem>
9304
9305 <!--
9306 Author: Amit Langote <[email protected]>
9307 2025-04-04 [88f55bc97] Make derived clause lookup in EquivalenceClass more effi
9308 Author: David Rowley <[email protected]>
9309 2025-04-08 [d69d45a5a] Speedup child EquivalenceMember lookup in planner
9310 -->
9311
9312 <listitem>
9313 <para>
9314 Improve the efficiency of planning queries accessing many partitions
9315 (Ashutosh Bapat, Yuya Watari, David Rowley)
9316 <ulink url="&commit_baseurl;88f55bc97">&sect;</ulink>
9317 <ulink url="&commit_baseurl;d69d45a5a">&sect;</ulink>
9318 </para>
9319 </listitem>
9320
9321 <!--
9322 Author: Richard Guo <[email protected]>
9323 2024-07-30 [9b282a935] Fix partitionwise join with partially-redundant join cla
9324 Author: Richard Guo <[email protected]>
9325 2024-07-29 [513f4472a] Reduce memory used by partitionwise joins
9326 -->
9327
9328 <listitem>
9329 <para>
9330 Allow <link linkend="guc-enable-partitionwise-join">partitionwise
9331 joins</link> in more cases, and reduce its memory usage (Richard Guo,
9332 Tom Lane, Ashutosh Bapat)
9333 <ulink url="&commit_baseurl;9b282a935">&sect;</ulink>
9334 <ulink url="&commit_baseurl;513f4472a">&sect;</ulink>
9335 </para>
9336 </listitem>
9337
9338 <!--
9339 Author: Alexander Korotkov <[email protected]>
9340 2025-03-10 [fae535da0] Teach Append to consider tuple_fraction when accumulatin
9341 -->
9342
9343 <listitem>
9344 <para>
9345 Improve cost estimates of partition queries (Nikita Malakhov,
9346 Andrei Lepikhov)
9347 <ulink url="&commit_baseurl;fae535da0">&sect;</ulink>
9348 </para>
9349 </listitem>
9350
9351 <!--
9352 Author: Tom Lane <[email protected]>
9353 2025-04-02 [0dca5d68d] Change SQL-language functions to use the plan cache.
9354 Author: Tom Lane <[email protected]>
9355 2025-04-17 [09b07c295] Minor performance improvement for SQL-language functions
9356 -->
9357
9358 <listitem>
9359 <para>
9360 Improve <link linkend="xfunc-sql"><acronym>SQL</acronym>-language
9361 function</link> plan caching (Alexander Pyhalov, Tom Lane)
9362 <ulink url="&commit_baseurl;0dca5d68d">&sect;</ulink>
9363 <ulink url="&commit_baseurl;09b07c295">&sect;</ulink>
9364 </para>
9365 </listitem>
9366
9367 <!--
9368 Author: Robert Haas <[email protected]>
9369 2024-08-21 [e22253467] Treat number of disabled nodes in a path as a separate c
9370 -->
9371
9372 <listitem>
9373 <para>
9374 Improve handling of disabled optimizer features (Robert Haas)
9375 <ulink url="&commit_baseurl;e22253467">&sect;</ulink>
9376 </para>
9377 </listitem>
9378
9379 </itemizedlist>
9380
9381 </sect4>
9382
9383 <sect4 id="release-18-indexes">
9384 <title>Indexes</title>
9385
9386 <itemizedlist>
9387
9388 <!--
9389 Author: Peter Geoghegan <[email protected]>
9390 2025-04-04 [92fe23d93] Add nbtree skip scan optimization.
9391 Author: Peter Geoghegan <[email protected]>
9392 2025-04-04 [8a510275d] Further optimize nbtree search scan key comparisons.
9393 -->
9394
9395 <listitem>
9396 <para>
9397 Allow skip scans of <link linkend="xfunc-sql">btree</link> indexes
9398 (Peter Geoghegan)
9399 <ulink url="&commit_baseurl;92fe23d93">&sect;</ulink>
9400 <ulink url="&commit_baseurl;8a510275d">&sect;</ulink>
9401 </para>
9402
9403 <para>
9404 This allows multi-column btree indexes to be used in more cases such
9405 as when there are no restrictions on the first or early indexed
9406 columns (or there are non-equality ones), and there are useful
9407 restrictions on later indexed columns.
9408 </para>
9409 </listitem>
9410
9411 <!--
9412 Author: Peter Eisentraut <[email protected]>
9413 2025-03-18 [f278e1fe3] Allow non-btree unique indexes for partition keys
9414 Author: Peter Eisentraut <[email protected]>
9415 2025-03-18 [9d6db8bec] Allow non-btree unique indexes for matviews
9416 -->
9417
9418 <listitem>
9419 <para>
9420 Allow non-btree unique indexes to be used as partition keys and in
9421 materialized views (Mark Dilger)
9422 <ulink url="&commit_baseurl;f278e1fe3">&sect;</ulink>
9423 <ulink url="&commit_baseurl;9d6db8bec">&sect;</ulink>
9424 </para>
9425
9426 <para>
9427 The index type must still support equality.
9428 </para>
9429 </listitem>
9430
9431 <!--
9432 Author: Tomas Vondra <[email protected]>
9433 2025-03-03 [8492feb98] Allow parallel CREATE INDEX for GIN indexes
9434 -->
9435
9436 <listitem>
9437 <para>
9438 Allow <link linkend="gin"><literal>GIN</literal></link> indexes to
9439 be created in parallel (Tomas Vondra, Matthias van de Meent)
9440 <ulink url="&commit_baseurl;8492feb98">&sect;</ulink>
9441 </para>
9442 </listitem>
9443
9444 <!--
9445 Author: Heikki Linnakangas <[email protected]>
9446 2025-04-02 [e9e7b6604] Add GiST and btree sortsupport routines for range types
9447 -->
9448
9449 <listitem>
9450 <para>
9451 Allow values to be sorted to speed range-type <link
9452 linkend="gist">GiST</link> and <link linkend="btree">btree</link>
9453 index builds (Bernd Helmle)
9454 <ulink url="&commit_baseurl;e9e7b6604">&sect;</ulink>
9455 </para>
9456 </listitem>
9457
9458 </itemizedlist>
9459
9460 </sect4>
9461
9462 <sect4 id="release-18-performance">
9463 <title>General Performance</title>
9464
9465 <itemizedlist>
9466
9467 <!--
9468 Author: Andres Freund <[email protected]>
9469 2025-03-17 [02844012b] aio: Basic subsystem initialization
9470 Author: Andres Freund <[email protected]>
9471 2025-03-17 [da7226993] aio: Add core asynchronous I/O infrastructure
9472 Author: Andres Freund <[email protected]>
9473 2025-03-18 [55b454d0e] aio: Infrastructure for io_method=worker
9474 Author: Andres Freund <[email protected]>
9475 2025-03-18 [247ce06b8] aio: Add io_method=worker
9476 Author: Thomas Munro <[email protected]>
9477 2025-03-19 [10f664684] Introduce io_max_combine_limit.
9478 Author: Thomas Munro <[email protected]>
9479 2025-03-19 [06fb5612c] Increase io_combine_limit range to 1MB.
9480 Author: Andres Freund <[email protected]>
9481 2025-03-26 [c325a7633] aio: Add io_method=io_uring
9482 Author: Andres Freund <[email protected]>
9483 2025-03-29 [50cb7505b] aio: Implement support for reads in smgr/md/fd
9484 Author: Andres Freund <[email protected]>
9485 2025-03-30 [047cba7fa] bufmgr: Implement AIO read support
9486 Author: Andres Freund <[email protected]>
9487 2025-03-30 [12ce89fd0] bufmgr: Use AIO in StartReadBuffers()
9488 Author: Andres Freund <[email protected]>
9489 2025-03-30 [2a5e709e7] Enable IO concurrency on all systems
9490 -->
9491
9492 <listitem>
9493 <para>
9494 Add an asynchronous I/O subsystem (Andres Freund, Thomas Munro,
9495 Nazir Bilal Yavuz, Melanie Plageman)
9496 <ulink url="&commit_baseurl;02844012b">&sect;</ulink>
9497 <ulink url="&commit_baseurl;da7226993">&sect;</ulink>
9498 <ulink url="&commit_baseurl;55b454d0e">&sect;</ulink>
9499 <ulink url="&commit_baseurl;247ce06b8">&sect;</ulink>
9500 <ulink url="&commit_baseurl;10f664684">&sect;</ulink>
9501 <ulink url="&commit_baseurl;06fb5612c">&sect;</ulink>
9502 <ulink url="&commit_baseurl;c325a7633">&sect;</ulink>
9503 <ulink url="&commit_baseurl;50cb7505b">&sect;</ulink>
9504 <ulink url="&commit_baseurl;047cba7fa">&sect;</ulink>
9505 <ulink url="&commit_baseurl;12ce89fd0">&sect;</ulink>
9506 <ulink url="&commit_baseurl;2a5e709e7">&sect;</ulink>
9507 </para>
9508
9509 <para>
9510 This feature allows backends to queue multiple read requests,
9511 which allows for more efficient sequential scans, bitmap
9512 heap scans, vacuums, etc. This is enabled by server
9513 variable <xref linkend="guc-io-method"/>, with server
9514 variables <xref linkend="guc-io-combine-limit"/> and <xref
9515 linkend="guc-io-max-combine-limit"/> added to control it.
9516 This also enables <xref linkend="guc-effective-io-concurrency"/>
9517 and <xref linkend="guc-maintenance-io-concurrency"/>
9518 values greater than zero for systems without
9519 <function>fadvise()</function> support. The new system view <link
9520 linkend="view-pg-aios"><structname>pg_aios</structname></link>
9521 shows the file handles being used for asynchronous I/O.
9522 </para>
9523 </listitem>
9524
9525 <!--
9526 Author: Tomas Vondra <[email protected]>
9527 2024-09-21 [c4d5cb71d] Increase the number of fast-path lock slots
9528 -->
9529
9530 <listitem>
9531 <para>
9532 Improve the locking performance of queries that access many relations
9533 (Tomas Vondra)
9534 <ulink url="&commit_baseurl;c4d5cb71d">&sect;</ulink>
9535 </para>
9536 </listitem>
9537
9538 <!--
9539 Author: David Rowley <[email protected]>
9540 2024-08-20 [adf97c156] Speed up Hash Join by making ExprStates support hashing
9541 Author: David Rowley <[email protected]>
9542 2024-12-11 [0f5738202] Use ExprStates for hashing in GROUP BY and SubPlans
9543 Author: Jeff Davis <[email protected]>
9544 2025-03-24 [4d143509c] Create accessor functions for TupleHashEntry.
9545 Author: Jeff Davis <[email protected]>
9546 2025-03-24 [a0942f441] Add ExecCopySlotMinimalTupleExtra().
9547 Author: Jeff Davis <[email protected]>
9548 2025-03-24 [626df47ad] Remove 'additional' pointer from TupleHashEntryData.
9549 -->
9550
9551 <listitem>
9552 <para>
9553 Improve the performance and reduce memory usage of hash joins and
9554 <link linkend="sql-groupby"><literal>GROUP BY</literal></link>
9555 (David Rowley, Jeff Davis)
9556 <ulink url="&commit_baseurl;adf97c156">&sect;</ulink>
9557 <ulink url="&commit_baseurl;0f5738202">&sect;</ulink>
9558 <ulink url="&commit_baseurl;4d143509c">&sect;</ulink>
9559 <ulink url="&commit_baseurl;a0942f441">&sect;</ulink>
9560 <ulink url="&commit_baseurl;626df47ad">&sect;</ulink>
9561 </para>
9562
9563 <para>
9564 This also improves hash set operations used by <link
9565 linkend="sql-except"><literal>EXCEPT</literal></link>, and hash
9566 lookups of subplan values.
9567 </para>
9568 </listitem>
9569
9570 <!--
9571 Author: Melanie Plageman <[email protected]>
9572 2025-02-11 [052026c9b] Eagerly scan all-visible pages to amortize aggressive va
9573 Author: Melanie Plageman <[email protected]>
9574 2025-03-03 [06eae9e62] Trigger more frequent autovacuums with relallfrozen
9575 -->
9576
9577 <listitem>
9578 <para>
9579 Allow normal vacuums to freeze some pages, even though they are
9580 all-visible (Melanie Plageman)
9581 <ulink url="&commit_baseurl;052026c9b">&sect;</ulink>
9582 <ulink url="&commit_baseurl;06eae9e62">&sect;</ulink>
9583 </para>
9584
9585 <para>
9586 This reduces the overhead of later full-relation
9587 freezing. The aggressiveness of this can be
9588 controlled by server variable and per-table setting <xref
9589 linkend="guc-vacuum-max-eager-freeze-failure-rate"/>. Previously
9590 vacuum never processed all-visible pages until freezing was required.
9591 </para>
9592 </listitem>
9593
9594 <!--
9595 Author: Nathan Bossart <[email protected]>
9596 2025-03-20 [0164a0f9e] Add vacuum_truncate configuration parameter.
9597 -->
9598
9599 <listitem>
9600 <para>
9601 Add server variable <xref linkend="guc-vacuum-truncate"/> to control
9602 file truncation during <xref linkend="sql-vacuum"/> (Nathan Bossart,
9603 Gurjeet Singh)
9604 <ulink url="&commit_baseurl;0164a0f9e">&sect;</ulink>
9605 </para>
9606
9607 <para>
9608 A storage-level parameter with the same name and behavior already
9609 existed.
9610 </para>
9611 </listitem>
9612
9613 <!--
9614 Author: Melanie Plageman <[email protected]>
9615 2025-03-12 [ff79b5b2a] Increase default effective_io_concurrency to 16
9616 Author: Melanie Plageman <[email protected]>
9617 2025-03-18 [cc6be07eb] Increase default maintenance_io_concurrency to 16
9618 -->
9619
9620 <listitem>
9621 <para>
9622 Increase server variables <xref
9623 linkend="guc-effective-io-concurrency"/>'s and <xref
9624 linkend="guc-maintenance-io-concurrency"/>'s default values to 16
9625 (Melanie Plageman)
9626 <ulink url="&commit_baseurl;ff79b5b2a">&sect;</ulink>
9627 <ulink url="&commit_baseurl;cc6be07eb">&sect;</ulink>
9628 </para>
9629
9630 <para>
9631 This more accurately reflects modern hardware.
9632 </para>
9633 </listitem>
9634
9635 </itemizedlist>
9636
9637 </sect4>
9638
9639 <sect4 id="release-18-monitoring">
9640 <title>Monitoring</title>
9641
9642 <itemizedlist>
9643
9644 <!--
9645 Author: Melanie Plageman <[email protected]>
9646 2025-03-12 [9219093ca] Modularize log_connections output
9647 -->
9648
9649 <listitem>
9650 <para>
9651 Increase the logging granularity of server variable <xref
9652 linkend="guc-log-connections"/> (Melanie Plageman)
9653 <ulink url="&commit_baseurl;9219093ca">&sect;</ulink>
9654 </para>
9655
9656 <para>
9657 This server variable was previously only boolean, which is still
9658 supported.
9659 </para>
9660 </listitem>
9661
9662 <!--
9663 Author: Melanie Plageman <[email protected]>
9664 2025-03-12 [18cd15e70] Add connection establishment duration logging
9665 -->
9666
9667 <listitem>
9668 <para>
9669 Add <varname>log_connections</varname> option to report the duration
9670 of connection stages (Melanie Plageman)
9671 <ulink url="&commit_baseurl;18cd15e70">&sect;</ulink>
9672 </para>
9673 </listitem>
9674
9675 <!--
9676 Author: Tom Lane <[email protected]>
9677 2025-04-07 [3516ea768] Add local-address escape "%L" to log_line_prefix.
9678 -->
9679
9680 <listitem>
9681 <para>
9682 Add <xref linkend="guc-log-line-prefix"/> escape
9683 <literal>%L</literal> to output the client <acronym>IP</acronym>
9684 address (Greg Sabino Mullane)
9685 <ulink url="&commit_baseurl;3516ea768">&sect;</ulink>
9686 </para>
9687 </listitem>
9688
9689 <!--
9690 Author: Fujii Masao <[email protected]>
9691 2025-03-14 [6d376c3b0] Add GUC option to log lock acquisition failures.
9692 Author: Fujii Masao <[email protected]>
9693 2025-06-03 [73bdcfab3] Rename log_lock_failure GUC to log_lock_failures for con
9694 -->
9695
9696 <listitem>
9697 <para>
9698 Add server variable <xref linkend="guc-log-lock-failures"/> to log
9699 lock acquisition failures (Yuki Seino, Fujii Masao)
9700 <ulink url="&commit_baseurl;6d376c3b0">&sect;</ulink>
9701 <ulink url="&commit_baseurl;73bdcfab3">&sect;</ulink>
9702 </para>
9703
9704 <para>
9705 Specifically it reports <link
9706 linkend="sql-for-update-share"><command>SELECT
9707 ... NOWAIT</command></link> lock failures.
9708 </para>
9709 </listitem>
9710
9711 <!--
9712 Author: Michael Paquier <[email protected]>
9713 2025-01-28 [30a6ed0ce] Track per-relation cumulative time spent in [auto]vacuum
9714 -->
9715
9716 <listitem>
9717 <para>
9718 Modify <link
9719 linkend="monitoring-pg-stat-all-tables-view"><structname>pg_stat_all_tables</structname></link>
9720 and its variants to report the time spent in <xref
9721 linkend="sql-vacuum"/>, <xref linkend="sql-analyze"/>, and their
9722 <link linkend="autovacuum">automatic</link> variants (Sami Imseih)
9723 <ulink url="&commit_baseurl;30a6ed0ce">&sect;</ulink>
9724 </para>
9725
9726 <para>
9727 The new columns are <structfield>total_vacuum_time</structfield>,
9728 <structfield>total_autovacuum_time</structfield>,
9729 <structfield>total_analyze_time</structfield>, and
9730 <structfield>total_autoanalyze_time</structfield>.
9731 </para>
9732 </listitem>
9733
9734 <!--
9735 Author: Nathan Bossart <[email protected]>
9736 2025-02-11 [bb8dff999] Add cost-based vacuum delay time to progress views.
9737 Author: Nathan Bossart <[email protected]>
9738 2025-02-14 [7720082ae] Add delay time to VACUUM/ANALYZE (VERBOSE) and autovacuu
9739 -->
9740
9741 <listitem>
9742 <para>
9743 Add delay time reporting to <xref linkend="sql-vacuum"/> and <xref
9744 linkend="sql-analyze"/> (Bertrand Drouvot, Nathan Bossart)
9745 <ulink url="&commit_baseurl;bb8dff999">&sect;</ulink>
9746 <ulink url="&commit_baseurl;7720082ae">&sect;</ulink>
9747 </para>
9748
9749 <para>
9750 This information appears in the server log, the system views <link
9751 linkend="vacuum-progress-reporting"><structname>pg_stat_progress_vacuum</structname></link>
9752 and <link
9753 linkend="pg-stat-progress-analyze-view"><structname>pg_stat_progress_analyze</structname></link>,
9754 and the output of <xref linkend="sql-vacuum"/> and <xref
9755 linkend="sql-analyze"/> when in <literal>VERBOSE</literal>
9756 mode; tracking must be enabled with the server variable <xref
9757 linkend="guc-track-cost-delay-timing"/>.
9758 </para>
9759 </listitem>
9760
9761 <!--
9762 Author: Masahiko Sawada <[email protected]>
9763 2024-08-13 [4c1b4cdb8] Add resource statistics reporting to ANALYZE VERBOSE.
9764 Author: Masahiko Sawada <[email protected]>
9765 2024-09-09 [bb7775234] Add WAL usage reporting to ANALYZE VERBOSE output.
9766 -->
9767
9768 <listitem>
9769 <para>
9770 Add <acronym>WAL</acronym>, <acronym>CPU</acronym>, and average
9771 read statistics output to <command>ANALYZE VERBOSE</command>
9772 (Anthonin Bonnefoy)
9773 <ulink url="&commit_baseurl;4c1b4cdb8">&sect;</ulink>
9774 <ulink url="&commit_baseurl;bb7775234">&sect;</ulink>
9775 </para>
9776 </listitem>
9777
9778 <!--
9779 Author: Michael Paquier <[email protected]>
9780 2025-02-17 [6a8a7ce47] Add information about WAL buffers full to VACUUM/ANALYZE
9781 -->
9782
9783 <listitem>
9784 <para>
9785 Add full <acronym>WAL</acronym> buffer count to
9786 <command>VACUUM</command>/<command>ANALYZE (VERBOSE)</command>
9787 and autovacuum log output (Bertrand Drouvot)
9788 <ulink url="&commit_baseurl;6a8a7ce47">&sect;</ulink>
9789 </para>
9790 </listitem>
9791
9792 <!--
9793 Author: Michael Paquier <[email protected]>
9794 2024-12-19 [9aea73fc6] Add backend-level statistics to pgstats
9795 Author: Michael Paquier <[email protected]>
9796 2025-03-03 [3f1db99bf] Handle auxiliary processes in SQL functions of backend s
9797 -->
9798
9799 <listitem>
9800 <para>
9801 Add per-backend I/O statistics reporting (Bertrand Drouvot)
9802 <ulink url="&commit_baseurl;9aea73fc6">&sect;</ulink>
9803 <ulink url="&commit_baseurl;3f1db99bf">&sect;</ulink>
9804 </para>
9805
9806 <para>
9807 The statistics are accessed via <link
9808 linkend="pg-stat-get-backend-io"><function>pg_stat_get_backend_io()</function></link>.
9809 Per-backend I/O statistics can be cleared via <link
9810 linkend="monitoring-stats-funcs-table"><function>pg_stat_reset_backend_stats()</function></link>.
9811 </para>
9812 </listitem>
9813
9814 <!--
9815 Author: Michael Paquier <[email protected]>
9816 2025-01-14 [f92c854cf] Make pg_stat_io count IOs as bytes instead of blocks for
9817 -->
9818
9819 <listitem>
9820 <para>
9821 Add <link
9822 linkend="monitoring-pg-stat-io-view"><structname>pg_stat_io</structname></link>
9823 columns to report I/O activity in bytes (Nazir Bilal Yavuz)
9824 <ulink url="&commit_baseurl;f92c854cf">&sect;</ulink>
9825 </para>
9826
9827 <para>
9828 The new columns are <structfield>read_bytes</structfield>,
9829 <structfield>write_bytes</structfield>, and
9830 <structfield>extend_bytes</structfield>. The
9831 <structfield>op_bytes</structfield> column, which always equaled
9832 <link linkend="guc-block-size"><varname>BLCKSZ</varname></link>,
9833 has been removed.
9834 </para>
9835 </listitem>
9836
9837 <!--
9838 Author: Michael Paquier <[email protected]>
9839 2025-02-04 [a051e71e2] Add data for WAL in pg_stat_io and backend statistics
9840 Author: Michael Paquier <[email protected]>
9841 2025-02-20 [4538bd3f1] doc: Add details about object "wal" in pg_stat_io
9842 Author: Michael Paquier <[email protected]>
9843 2025-03-06 [7f7f324eb] Add more monitoring data for WAL writes in the WAL recei
9844 -->
9845
9846 <listitem>
9847 <para>
9848 Add <acronym>WAL</acronym> I/O activity rows to
9849 <structname>pg_stat_io</structname> (Nazir Bilal Yavuz, Bertrand
9850 Drouvot, Michael Paquier)
9851 <ulink url="&commit_baseurl;a051e71e2">&sect;</ulink>
9852 <ulink url="&commit_baseurl;4538bd3f1">&sect;</ulink>
9853 <ulink url="&commit_baseurl;7f7f324eb">&sect;</ulink>
9854 </para>
9855
9856 <para>
9857 This includes <acronym>WAL</acronym> receiver activity and a wait
9858 event for such writes.
9859 </para>
9860
9861 </listitem>
9862
9863 <!--
9864 Author: Michael Paquier <[email protected]>
9865 2025-02-26 [6c349d83b] Re-add GUC track_wal_io_timing
9866 -->
9867
9868 <listitem>
9869 <para>
9870 Change server variable <xref linkend="guc-track-wal-io-timing"/>
9871 to control tracking <acronym>WAL</acronym> timing
9872 in <structname>pg_stat_io</structname> instead of <link
9873 linkend="pg-stat-wal-view"><structname>pg_stat_wal</structname></link>
9874 (Bertrand Drouvot)
9875 <ulink url="&commit_baseurl;6c349d83b">&sect;</ulink>
9876 </para>
9877 </listitem>
9878
9879 <!--
9880 Author: Michael Paquier <[email protected]>
9881 2025-02-24 [2421e9a51] Remove read/sync fields from pg_stat_wal and GUC track_w
9882 Author: Michael Paquier <[email protected]>
9883 2025-02-26 [6c349d83b] Re-add GUC track_wal_io_timing
9884 -->
9885
9886 <listitem>
9887 <para>
9888 Remove read/sync columns from <structname>pg_stat_wal</structname>
9889 (Bertrand Drouvot)
9890 <ulink url="&commit_baseurl;2421e9a51">&sect;</ulink>
9891 <ulink url="&commit_baseurl;6c349d83b">&sect;</ulink>
9892 </para>
9893
9894 <para>
9895 This removes columns <structfield>wal_write</structfield>,
9896 <structfield>wal_sync</structfield>,
9897 <structfield>wal_write_time</structfield>, and
9898 <structfield>wal_sync_time</structfield>.
9899 </para>
9900 </listitem>
9901
9902 <!--
9903 Author: Michael Paquier <[email protected]>
9904 2025-03-11 [76def4cdd] Add WAL data to backend statistics
9905 -->
9906
9907 <listitem>
9908 <para>
9909 Add function <link
9910 linkend="pg-stat-get-backend-wal"><function>pg_stat_get_backend_wal()</function></link>
9911 to return per-backend <acronym>WAL</acronym> statistics (Bertrand
9912 Drouvot)
9913 <ulink url="&commit_baseurl;76def4cdd">&sect;</ulink>
9914 </para>
9915
9916 <para>
9917 Per-backend <acronym>WAL</acronym>
9918 statistics can be cleared via <link
9919 linkend="monitoring-stats-funcs-table"><function>pg_stat_reset_backend_stats()</function></link>.
9920 </para>
9921 </listitem>
9922
9923 <!--
9924 Author: Nathan Bossart <[email protected]>
9925 2024-10-11 [4e1fad378] Add pg_ls_summariesdir().
9926 -->
9927
9928 <listitem>
9929 <para>
9930 Add function <link
9931 linkend="functions-admin-genfile-table"><function>pg_ls_summariesdir()</function></link>
9932 to specifically list the contents of <link
9933 linkend="storage-file-layout"><envar>PGDATA</envar></link>/<link
9934 linkend="guc-wal-summary-keep-time"><filename>pg_wal/summaries</filename></link>
9935 (Yushi Ogiwara)
9936 <ulink url="&commit_baseurl;4e1fad378">&sect;</ulink>
9937 </para>
9938 </listitem>
9939
9940 <!--
9941 Author: Fujii Masao <[email protected]>
9942 2024-09-30 [559efce1d] Add num_done counter to the pg_stat_checkpointer view.
9943 -->
9944
9945 <listitem>
9946 <para>
9947 Add column <link
9948 linkend="monitoring-pg-stat-checkpointer-view"><structname>pg_stat_checkpointer</structname></link>.<structfield>num_done</structfield>
9949 to report the number of completed checkpoints (Anton A. Melnikov)
9950 <ulink url="&commit_baseurl;559efce1d">&sect;</ulink>
9951 </para>
9952
9953 <para>
9954 Columns <structfield>num_timed</structfield> and
9955 <structfield>num_requested</structfield> count both completed and
9956 skipped checkpoints.
9957 </para>
9958 </listitem>
9959
9960 <!--
9961 Author: Fujii Masao <[email protected]>
9962 2024-10-02 [17cc5f666] Fix inconsistent reporting of checkpointer stats.
9963 -->
9964
9965 <listitem>
9966 <para>
9967 Add column
9968 <structname>pg_stat_checkpointer</structname>.<structfield>slru_written</structfield>
9969 to report <acronym>SLRU</acronym> buffers written (Nitin Jadhav)
9970 <ulink url="&commit_baseurl;17cc5f666">&sect;</ulink>
9971 </para>
9972
9973 <para>
9974 Also, modify the checkpoint server log message to report separate
9975 shared buffer and <acronym>SLRU</acronym> buffer values.
9976 </para>
9977 </listitem>
9978
9979 <!--
9980 Author: Michael Paquier <[email protected]>
9981 2024-11-11 [e7a9496de] Add two attributes to pg_stat_database for parallel work
9982 -->
9983
9984 <listitem>
9985 <para>
9986 Add columns to <link
9987 linkend="monitoring-pg-stat-database-view"><structname>pg_stat_database</structname></link>
9988 to report parallel worker activity (Benoit Lobréau)
9989 <ulink url="&commit_baseurl;e7a9496de">&sect;</ulink>
9990 </para>
9991
9992 <para>
9993 The new columns are
9994 <structfield>parallel_workers_to_launch</structfield> and
9995 <structfield>parallel_workers_launched</structfield>.
9996 </para>
9997 </listitem>
9998
9999 <!--
10000 Author: Álvaro Herrera <[email protected]>
10001 2025-03-18 [62d712ecf] Introduce squashing of constant lists in query jumbling
10002 Author: Álvaro Herrera <[email protected]>
10003 2025-03-27 [9fbd53dea] Remove the query_id_squash_values GUC
10004 Author: Álvaro Herrera <[email protected]>
10005 Branch: master Release: REL_18_BR [c2da1a5d6] 2025-06-24 19:36:32 +0200
10006 -->
10007
10008 <listitem>
10009 <para>
10010 Have <link linkend="guc-compute-query-id">query id</link> computation
10011 of constant lists consider only the first and last constants (Dmitry
10012 Dolgov, Sami Imseih)
10013 <ulink url="&commit_baseurl;62d712ecf">&sect;</ulink>
10014 <ulink url="&commit_baseurl;9fbd53dea">&sect;</ulink>
10015 <ulink url="&commit_baseurl;c2da1a5d6">&sect;</ulink>
10016 </para>
10017
10018 <para>
10019 Jumbling is used by <xref linkend="pgstatstatements"/>.
10020 </para>
10021 </listitem>
10022
10023 <!--
10024 Author: Michael Paquier <[email protected]>
10025 2025-03-26 [787514b30] Use relation name instead of OID in query jumbling for R
10026 -->
10027
10028 <listitem>
10029 <para>
10030 Adjust query id computations to group together queries using the
10031 same relation name (Michael Paquier, Sami Imseih)
10032 <ulink url="&commit_baseurl;787514b30">&sect;</ulink>
10033 </para>
10034
10035 <para>
10036 This is true even if the tables in different schemas have different
10037 column names.
10038 </para>
10039 </listitem>
10040
10041 <!--
10042 Author: David Rowley <[email protected]>
10043 2024-07-01 [12227a1d5] Add context type field to pg_backend_memory_contexts
10044 -->
10045
10046 <listitem>
10047 <para>
10048 Add column <link
10049 linkend="view-pg-backend-memory-contexts"><structname>pg_backend_memory_contexts</structname></link>.<structfield>type</structfield>
10050 to report the type of memory context (David Rowley)
10051 <ulink url="&commit_baseurl;12227a1d5">&sect;</ulink>
10052 </para>
10053 </listitem>
10054
10055 <!--
10056 Author: David Rowley <[email protected]>
10057 2024-07-25 [32d3ed816] Add path column to pg_backend_memory_contexts view
10058 -->
10059
10060 <listitem>
10061 <para>
10062 Add column
10063 <structname>pg_backend_memory_contexts</structname>.<structfield>path</structfield>
10064 to show memory context parents (Melih Mutlu)
10065 <ulink url="&commit_baseurl;32d3ed816">&sect;</ulink>
10066 </para>
10067 </listitem>
10068
10069 </itemizedlist>
10070
10071 </sect4>
10072
10073 <sect4 id="release-18-privileges">
10074 <title>Privileges</title>
10075
10076 <itemizedlist>
10077
10078 <!--
10079 Author: Michael Paquier <[email protected]>
10080 2024-07-04 [4564f1ceb] Add pg_get_acl() to get the ACL for a database object
10081 Author: Michael Paquier <[email protected]>
10082 2024-07-10 [d898665bf] Extend pg_get_acl() to handle sub-object IDs
10083 -->
10084
10085 <listitem>
10086 <para>
10087 Add function <link
10088 linkend="functions-info-object-table"><function>pg_get_acl()</function></link>
10089 to retrieve database access control details (Joel Jacobson)
10090 <ulink url="&commit_baseurl;4564f1ceb">&sect;</ulink>
10091 <ulink url="&commit_baseurl;d898665bf">&sect;</ulink>
10092 </para>
10093 </listitem>
10094
10095 <!--
10096 Author: Fujii Masao <[email protected]>
10097 2024-09-12 [4eada203a] Add has_largeobject_privilege function.
10098 -->
10099
10100 <listitem>
10101 <para>
10102 Add function <link
10103 linkend="functions-info-access-table"><function>has_largeobject_privilege()</function></link>
10104 to check large object privileges (Yugo Nagata)
10105 <ulink url="&commit_baseurl;4eada203a">&sect;</ulink>
10106 </para>
10107 </listitem>
10108
10109 <!--
10110 Author: Fujii Masao <[email protected]>
10111 2025-04-04 [0d6c47766] Extend ALTER DEFAULT PRIVILEGES to define default privil
10112 -->
10113
10114 <listitem>
10115 <para>
10116 Allow <xref linkend="sql-alterdefaultprivileges"/> to define
10117 large object default privileges (Takatsuka Haruka, Yugo Nagata,
10118 Laurenz Albe)
10119 <ulink url="&commit_baseurl;0d6c47766">&sect;</ulink>
10120 </para>
10121 </listitem>
10122
10123 <!--
10124 Author: Nathan Bossart <[email protected]>
10125 2024-07-09 [ccd38024b] Introduce pg_signal_autovacuum_worker.
10126 -->
10127
10128 <listitem>
10129 <para>
10130 Add predefined role <link
10131 linkend="predefined-roles"><literal>pg_signal_autovacuum_worker</literal></link>
10132 (Kirill Reshke)
10133 <ulink url="&commit_baseurl;ccd38024b">&sect;</ulink>
10134 </para>
10135
10136 <para>
10137 This allows sending signals to autovacuum workers.
10138 </para>
10139 </listitem>
10140
10141 </itemizedlist>
10142
10143 </sect4>
10144
10145 <sect4 id="release-18-server-config">
10146 <title>Server Configuration</title>
10147
10148 <itemizedlist>
10149
10150 <!--
10151 Author: Daniel Gustafsson <[email protected]>
10152 2025-02-20 [b3f0be788] Add support for OAUTHBEARER SASL mechanism
10153 -->
10154
10155 <listitem>
10156 <para>
10157 Add support for the <link linkend="auth-oauth">OAuth authentication
10158 method</link> (Jacob Champion, Daniel Gustafsson, Thomas Munro)
10159 <ulink url="&commit_baseurl;b3f0be788">&sect;</ulink>
10160 </para>
10161
10162 <para>
10163 This adds an <literal>oauth</literal> authentication method to <link
10164 linkend="auth-pg-hba-conf"><filename>pg_hba.conf</filename></link>,
10165 libpq OAuth options, a server variable <xref
10166 linkend="guc-oauth-validator-libraries"/> to load
10167 token validation libraries, and a configure flag <link
10168 linkend="configure-option-with-libcurl"><option>--with-libcurl</option></link>
10169 to add the required compile-time libraries.
10170 </para>
10171 </listitem>
10172
10173 <!--
10174 Author: Daniel Gustafsson <[email protected]>
10175 2024-10-24 [45188c2ea] Support configuring TLSv1.3 cipher suites
10176 -->
10177
10178 <listitem>
10179 <para>
10180 Add server variable <xref linkend="guc-ssl-tls13-ciphers"/> to allow
10181 specification of multiple colon-separated TLSv1.3 cipher suites
10182 (Erica Zhang, Daniel Gustafsson)
10183 <ulink url="&commit_baseurl;45188c2ea">&sect;</ulink>
10184 </para>
10185 </listitem>
10186
10187 <!--
10188 Author: Daniel Gustafsson <[email protected]>
10189 2025-03-18 [daa02c6bd] Add X25519 to the default set of curves
10190 -->
10191
10192 <listitem>
10193 <para>
10194 Change server variable <xref linkend="guc-ssl-groups"/>'s default
10195 to include elliptic curve X25519 (Daniel Gustafsson, Jacob Champion)
10196 <ulink url="&commit_baseurl;daa02c6bd">&sect;</ulink>
10197 </para>
10198 </listitem>
10199
10200 <!--
10201 Author: Daniel Gustafsson <[email protected]>
10202 2024-10-24 [3d1ef3a15] Support configuring multiple ECDH curves
10203 -->
10204
10205 <listitem>
10206 <para>
10207 Rename server variable <varname>ssl_ecdh_curve</varname> to <xref
10208 linkend="guc-ssl-groups"/> and allow multiple colon-separated
10209 <acronym>ECDH</acronym> curves to be specified (Erica Zhang,
10210 Daniel Gustafsson)
10211 <ulink url="&commit_baseurl;3d1ef3a15">&sect;</ulink>
10212 </para>
10213
10214 <para>
10215 The previous name still works.
10216 </para>
10217 </listitem>
10218
10219 <!--
10220 Author: Heikki Linnakangas <[email protected]>
10221 2025-04-02 [a460251f0] Make cancel request keys longer
10222 Author: Heikki Linnakangas <[email protected]>
10223 2024-07-29 [9d9b9d46f] Move cancel key generation to after forking the backend
10224 -->
10225
10226 <listitem>
10227 <para>
10228 Make <link linkend="functions-admin-signal-table">cancel request
10229 keys</link> 256 bits (Heikki Linnakangas, Jelte Fennema-Nio)
10230 <ulink url="&commit_baseurl;a460251f0">&sect;</ulink>
10231 <ulink url="&commit_baseurl;9d9b9d46f">&sect;</ulink>
10232 </para>
10233
10234 <para>
10235 This is only possible when the server and client support wire
10236 protocol version 3.2, introduced in this release.
10237 </para>
10238 </listitem>
10239
10240 <!--
10241 Author: Nathan Bossart <[email protected]>
10242 2025-01-06 [c758119e5] Allow changing autovacuum_max_workers without restarting
10243 -->
10244
10245 <listitem>
10246 <para>
10247 Add server variable <xref linkend="guc-autovacuum-worker-slots"/>
10248 to specify the maximum number of background workers (Nathan Bossart)
10249 <ulink url="&commit_baseurl;c758119e5">&sect;</ulink>
10250 </para>
10251
10252 <para>
10253 With this variable set, <xref linkend="guc-autovacuum-max-workers"/>
10254 can be adjusted at runtime up to this maximum without a server
10255 restart.
10256 </para>
10257 </listitem>
10258
10259 <!--
10260 Author: Nathan Bossart <[email protected]>
10261 2025-02-05 [306dc520b] Introduce autovacuum_vacuum_max_threshold.
10262 -->
10263
10264 <listitem>
10265 <para>
10266 Allow specification of the fixed number of dead tuples that will
10267 trigger an <link linkend="autovacuum">autovacuum</link> (Nathan
10268 Bossart, Frédéric Yhuel)
10269 <ulink url="&commit_baseurl;306dc520b">&sect;</ulink>
10270 </para>
10271
10272 <para>
10273 The server variable is <xref
10274 linkend="guc-autovacuum-vacuum-max-threshold"/>. Percentages are
10275 still used for triggering.
10276 </para>
10277 </listitem>
10278
10279 <!--
10280 Author: Andres Freund <[email protected]>
10281 2025-03-24 [adb5f85fa] Redefine max_files_per_process to control additionally o
10282 -->
10283
10284 <listitem>
10285 <para>
10286 Change server variable <xref linkend="guc-max-files-per-process"/>
10287 to limit only files opened by a backend (Andres Freund)
10288 <ulink url="&commit_baseurl;adb5f85fa">&sect;</ulink>
10289 </para>
10290
10291 <para>
10292 Previously files opened by the postmaster were also counted toward
10293 this limit.
10294 </para>
10295 </listitem>
10296
10297 <!--
10298 Author: Nathan Bossart <[email protected]>
10299 2024-07-26 [0dcaea569] Introduce num_os_semaphores GUC.
10300 -->
10301
10302 <listitem>
10303 <para>
10304 Add server variable <xref linkend="guc-num-os-semaphores"/> to
10305 report the required number of semaphores (Nathan Bossart)
10306 <ulink url="&commit_baseurl;0dcaea569">&sect;</ulink>
10307 </para>
10308
10309 <para>
10310 This is useful for operating system configuration.
10311 </para>
10312 </listitem>
10313
10314 <!--
10315 Author: Peter Eisentraut <[email protected]>
10316 2025-03-19 [4f7f7b037] extension_control_path
10317 Author: Peter Eisentraut <[email protected]>
10318 2025-05-02 [81eaaa2c4] Make "directory" setting work with extension_control_pat
10319 -->
10320
10321 <listitem>
10322 <para>
10323 Add server variable <xref linkend="guc-extension-control-path"/> to
10324 specify the location of extension control files (Peter Eisentraut,
10325 Matheus Alcantara)
10326 <ulink url="&commit_baseurl;4f7f7b037">&sect;</ulink>
10327 <ulink url="&commit_baseurl;81eaaa2c4">&sect;</ulink>
10328 </para>
10329 </listitem>
10330
10331 </itemizedlist>
10332
10333 </sect4>
10334
10335 <sect4 id="release-18-replication">
10336 <title>Streaming Replication and Recovery</title>
10337
10338 <itemizedlist>
10339
10340 <!--
10341 Author: Amit Kapila <[email protected]>
10342 2025-02-19 [ac0e33136] Invalidate inactive replication slots.
10343 -->
10344
10345 <listitem>
10346 <para>
10347 Allow inactive replication slots to be automatically invalidated using
10348 server variable <xref linkend="guc-idle-replication-slot-timeout"/>
10349 (Nisha Moond, Bharath Rupireddy)
10350 <ulink url="&commit_baseurl;ac0e33136">&sect;</ulink>
10351 </para>
10352 </listitem>
10353
10354 <!--
10355 Author: Masahiko Sawada <[email protected]>
10356 2025-03-21 [04ff636cb] Add GUC option to control maximum active replication ori
10357 -->
10358
10359 <listitem>
10360 <para>
10361 Add server variable <xref
10362 linkend="guc-max-active-replication-origins"/> to control the
10363 maximum active replication origins (Euler Taveira)
10364 <ulink url="&commit_baseurl;04ff636cb">&sect;</ulink>
10365 </para>
10366
10367 <para>
10368 This was previously controlled by <xref
10369 linkend="guc-max-replication-slots"/>, but this new setting allows
10370 a higher origin count in cases where fewer slots are required.
10371 </para>
10372 </listitem>
10373
10374 </itemizedlist>
10375
10376 </sect4>
10377
10378 <sect4 id="release-18-logical">
10379 <title><link linkend="logical-replication">Logical Replication</link></title>
10380
10381 <itemizedlist>
10382
10383 <!--
10384 Author: Amit Kapila <[email protected]>
10385 2024-10-30 [745217a05] Replicate generated columns when specified in the column
10386 Author: Amit Kapila <[email protected]>
10387 2024-11-07 [7054186c4] Replicate generated columns when 'publish_generated_colu
10388 Author: Amit Kapila <[email protected]>
10389 2024-12-04 [87ce27de6] Ensure stored generated columns must be published when r
10390 Author: Amit Kapila <[email protected]>
10391 2025-01-30 [6252b1eaf] Doc: Generated column replication.
10392 -->
10393
10394 <listitem>
10395 <para>
10396 Allow the values of <link
10397 linkend="sql-createtable-parms-generated-stored">generated
10398 columns</link> to be logically replicated (Shubham Khanna, Vignesh C,
10399 Zhijie Hou, Shlok Kyal, Peter Smith)
10400 <ulink url="&commit_baseurl;745217a05">&sect;</ulink>
10401 <ulink url="&commit_baseurl;7054186c4">&sect;</ulink>
10402 <ulink url="&commit_baseurl;87ce27de6">&sect;</ulink>
10403 <ulink url="&commit_baseurl;6252b1eaf">&sect;</ulink>
10404 </para>
10405
10406 <para>
10407 If the publication specifies a column list, all specified
10408 columns, generated and non-generated, are published.
10409 Without a specified column list, publication option
10410 <literal>publish_generated_columns</literal> controls whether
10411 generated columns are published. Previously generated columns
10412 were not replicated and the subscriber had to compute
10413 the values if possible; this is particularly useful for
10414 non-<productname>PostgreSQL</productname> subscribers which lack
10415 such a capability.
10416 </para>
10417 </listitem>
10418
10419 <!--
10420 Author: Amit Kapila <[email protected]>
10421 2024-10-28 [1bf1140be] Change the default value of the streaming option to 'par
10422 -->
10423
10424 <listitem>
10425 <para>
10426 Change the default <xref linkend="sql-createsubscription"/> streaming
10427 option from <literal>off</literal> to <literal>parallel</literal>
10428 (Vignesh C)
10429 <ulink url="&commit_baseurl;1bf1140be">&sect;</ulink>
10430 </para>
10431 </listitem>
10432
10433 <!--
10434 Author: Amit Kapila <[email protected]>
10435 2024-07-24 [1462aad2e] Allow altering of two_phase option of a SUBSCRIPTION.
10436 Author: Amit Kapila <[email protected]>
10437 2025-04-03 [4868c96bc] Fix slot synchronization for two_phase enabled slots.
10438 -->
10439
10440 <listitem>
10441 <para>
10442 Allow <xref linkend="sql-altersubscription"/> to change the
10443 replication slot's two-phase commit behavior (Hayato Kuroda, Ajin
10444 Cherian, Amit Kapila, Zhijie Hou)
10445 <ulink url="&commit_baseurl;1462aad2e">&sect;</ulink>
10446 <ulink url="&commit_baseurl;4868c96bc">&sect;</ulink>
10447 </para>
10448 </listitem>
10449
10450 <!--
10451 Author: Amit Kapila <[email protected]>
10452 2024-08-20 [9758174e2] Log the conflicts while applying changes in logical repl
10453 Author: Amit Kapila <[email protected]>
10454 2024-08-22 [edcb71258] Doc: explain the log format of logical replication confl
10455 Author: Amit Kapila <[email protected]>
10456 2024-08-29 [640178c92] Rename the conflict types for the origin differ cases.
10457 Author: Amit Kapila <[email protected]>
10458 2024-09-04 [6c2b5edec] Collect statistics about conflicts in logical replicatio
10459 Author: Amit Kapila <[email protected]>
10460 2025-03-24 [73eba5004] Detect and Log multiple_unique_conflicts type conflict.
10461 -->
10462
10463 <listitem>
10464 <para>
10465 Log <link linkend="hot-standby-conflict">conflicts</link> while
10466 applying logical replication changes (Zhijie Hou, Nisha Moond)
10467 <ulink url="&commit_baseurl;9758174e2">&sect;</ulink>
10468 <ulink url="&commit_baseurl;edcb71258">&sect;</ulink>
10469 <ulink url="&commit_baseurl;640178c92">&sect;</ulink>
10470 <ulink url="&commit_baseurl;6c2b5edec">&sect;</ulink>
10471 <ulink url="&commit_baseurl;73eba5004">&sect;</ulink>
10472 </para>
10473
10474 <para>
10475 Also report in new columns of <link
10476 linkend="monitoring-pg-stat-subscription-stats"><structname>pg_stat_subscription_stats</structname></link>.
10477 </para>
10478 </listitem>
10479
10480 </itemizedlist>
10481
10482 </sect4>
10483
10484 </sect3>
10485
10486 <sect3 id="release-18-utility">
10487 <title>Utility Commands</title>
10488
10489 <itemizedlist>
10490
10491 <!--
10492 Author: Peter Eisentraut <[email protected]>
10493 2025-02-07 [83ea6c540] Virtual generated columns
10494 Author: Peter Eisentraut <[email protected]>
10495 2025-03-28 [cdc168ad4] Add support for not-null constraints on virtual generate
10496 Author: Richard Guo <[email protected]>
10497 2025-02-25 [1e4351af3] Expand virtual generated columns in the planner
10498 -->
10499
10500 <listitem>
10501 <para>
10502 Allow <link linkend="sql-createtable-parms-generated-stored">generated
10503 columns</link> to be virtual, and make them the default (Peter
10504 Eisentraut, Jian He, Richard Guo, Dean Rasheed)
10505 <ulink url="&commit_baseurl;83ea6c540">&sect;</ulink>
10506 <ulink url="&commit_baseurl;cdc168ad4">&sect;</ulink>
10507 <ulink url="&commit_baseurl;1e4351af3">&sect;</ulink>
10508 </para>
10509
10510 <para>
10511 Virtual generated columns generate their values when the columns
10512 are read, not written. The write behavior can still be specified
10513 via the <literal>STORED</literal> option.
10514 </para>
10515 </listitem>
10516
10517 <!--
10518 Author: Dean Rasheed <[email protected]>
10519 2025-01-16 [80feb727c] Add OLD/NEW support to RETURNING in DML queries.
10520 -->
10521
10522 <listitem>
10523 <para>
10524 Add <literal>OLD</literal>/<literal>NEW</literal> support to <link
10525 linkend="dml-returning"><literal>RETURNING</literal></link> in
10526 <acronym>DML</acronym> queries (Dean Rasheed)
10527 <ulink url="&commit_baseurl;80feb727c">&sect;</ulink>
10528 </para>
10529
10530 <para>
10531 Previously <literal>RETURNING</literal> only returned new values for
10532 <xref linkend="sql-insert"/> and <xref linkend="sql-update"/>, and old
10533 values for <xref linkend="sql-delete"/>; <xref linkend="sql-merge"/>
10534 would return the appropriate value for the internal query executed.
10535 This new syntax allows the <literal>RETURNING</literal> list of
10536 <command>INSERT</command>/<command>UPDATE</command>/<command>DELETE</command>/<command>MERGE</command>
10537 to explicitly return old and new values by using the special aliases
10538 <literal>old</literal> and <literal>new</literal>. These aliases
10539 can be renamed to avoid identifier conflicts.
10540 </para>
10541 </listitem>
10542
10543 <!--
10544 Author: Michael Paquier <[email protected]>
10545 2025-02-19 [302cf1575] Add support for LIKE in CREATE FOREIGN TABLE
10546 -->
10547
10548 <listitem>
10549 <para>
10550 Allow foreign tables to be created like existing local tables
10551 (Zhang Mingli)
10552 <ulink url="&commit_baseurl;302cf1575">&sect;</ulink>
10553 </para>
10554
10555 <para>
10556 The syntax is <link linkend="sql-createforeigntable"><command>CREATE
10557 FOREIGN TABLE ... LIKE</command></link>.
10558 </para>
10559 </listitem>
10560
10561 <!--
10562 Author: Peter Eisentraut <[email protected]>
10563 2024-11-27 [85b7efa1c] Support LIKE with nondeterministic collations
10564 -->
10565
10566 <listitem>
10567 <para>
10568 Allow <link linkend="functions-like"><literal>LIKE</literal></link>
10569 with <link linkend="collation-nondeterministic">nondeterministic
10570 collations</link> (Peter Eisentraut)
10571 <ulink url="&commit_baseurl;85b7efa1c">&sect;</ulink>
10572 </para>
10573 </listitem>
10574
10575 <!--
10576 Author: Peter Eisentraut <[email protected]>
10577 2025-02-21 [329304c90] Support text position search functions with nondetermini
10578 -->
10579
10580 <listitem>
10581 <para>
10582 Allow text position search functions with nondeterministic collations
10583 (Peter Eisentraut)
10584 <ulink url="&commit_baseurl;329304c90">&sect;</ulink>
10585 </para>
10586
10587 <para>
10588 These used to generate an error.
10589 </para>
10590 </listitem>
10591
10592 <!--
10593 Author: Jeff Davis <[email protected]>
10594 2025-01-17 [d3d098316] Support PG_UNICODE_FAST locale in the builtin collation
10595 -->
10596
10597 <listitem>
10598 <para>
10599 Add builtin collation provider <link
10600 linkend="locale-providers"><literal>PG_UNICODE_FAST</literal></link>
10601 (Jeff Davis)
10602 <ulink url="&commit_baseurl;d3d098316">&sect;</ulink>
10603 </para>
10604
10605 <para>
10606 This locale supports case mapping, but sorts in code point order,
10607 not natural language order.
10608 </para>
10609 </listitem>
10610
10611 <!--
10612 Author: David Rowley <[email protected]>
10613 2024-09-24 [62ddf7ee9] Add ONLY support for VACUUM and ANALYZE
10614 -->
10615
10616 <listitem>
10617 <para>
10618 Allow <xref linkend="sql-vacuum"/> and <xref linkend="sql-analyze"/>
10619 to process partitioned tables without processing their children
10620 (Michael Harris)
10621 <ulink url="&commit_baseurl;62ddf7ee9">&sect;</ulink>
10622 </para>
10623
10624 <para>
10625 This is enabled with the new <literal>ONLY</literal> option. This is
10626 useful since autovacuum does not process partitioned tables, just
10627 its children.
10628 </para>
10629 </listitem>
10630
10631 <!--
10632 Author: Jeff Davis <[email protected]>
10633 2024-10-11 [e839c8ecc] Create functions pg_set_relation_stats, pg_clear_relatio
10634 Author: Jeff Davis <[email protected]>
10635 2024-10-24 [d32d14639] Add functions pg_restore_relation_stats(), pg_restore_at
10636 Author: Jeff Davis <[email protected]>
10637 2025-03-25 [650ab8aaf] Stats: use schemaname/relname instead of regclass.
10638 -->
10639
10640 <listitem>
10641 <para>
10642 Add functions to modify per-relation and per-column optimizer
10643 statistics (Corey Huinker)
10644 <ulink url="&commit_baseurl;e839c8ecc">&sect;</ulink>
10645 <ulink url="&commit_baseurl;d32d14639">&sect;</ulink>
10646 <ulink url="&commit_baseurl;650ab8aaf">&sect;</ulink>
10647 </para>
10648
10649 <para>
10650 The functions are <link
10651 linkend="functions-admin-statsmod"><function>pg_restore_relation_stats()</function></link>,
10652 <function>pg_restore_attribute_stats()</function>,
10653 <function>pg_clear_relation_stats()</function>, and
10654 <function>pg_clear_attribute_stats()</function>.
10655 </para>
10656 </listitem>
10657
10658
10659 <!--
10660 Author: Thomas Munro <[email protected]>
10661 2025-04-08 [f78ca6f3e] Introduce file_copy_method setting.
10662 -->
10663
10664 <listitem>
10665 <para>
10666 Add server variable <xref linkend="guc-file-copy-method"/> to control
10667 the file copying method (Nazir Bilal Yavuz)
10668 <ulink url="&commit_baseurl;f78ca6f3e">&sect;</ulink>
10669 </para>
10670
10671 <para>
10672 This controls whether <link
10673 linkend="sql-createdatabase"><command>CREATE DATABASE
10674 ... STRATEGY=FILE_COPY</command></link> and <link
10675 linkend="sql-alterdatabase"><command>ALTER DATABASE ... SET
10676 TABLESPACE</command></link> uses file copy or clone.
10677 </para>
10678 </listitem>
10679
10680 </itemizedlist>
10681
10682 <sect4 id="release-18-constraints">
10683 <title><link linkend="ddl-constraints">Constraints</link></title>
10684
10685 <itemizedlist>
10686
10687 <!--
10688 Author: Peter Eisentraut <[email protected]>
10689 2024-09-17 [fc0438b4e] Add temporal PRIMARY KEY and UNIQUE constraints
10690 Author: Peter Eisentraut <[email protected]>
10691 2024-09-17 [89f908a6d] Add temporal FOREIGN KEY contraints
10692 -->
10693
10694 <listitem>
10695 <para>
10696 Allow the specification of non-overlapping <link
10697 linkend="sql-createtable-parms-primary-key"><literal>PRIMARY
10698 KEY</literal></link>, <link linkend="sql-createtable-parms-unique">
10699 <literal>UNIQUE</literal></link>, and
10700 <link linkend="sql-createtable-parms-references">foreign key</link>
10701 constraints (Paul A. Jungwirth)
10702 <ulink url="&commit_baseurl;fc0438b4e">&sect;</ulink>
10703 <ulink url="&commit_baseurl;89f908a6d">&sect;</ulink>
10704 </para>
10705
10706 <para>
10707 This is specified by <literal>WITHOUT OVERLAPS</literal> for
10708 <literal>PRIMARY KEY</literal> and <literal>UNIQUE</literal>, and by
10709 <literal>PERIOD</literal> for foreign keys, all applied to the last
10710 specified column.
10711 </para>
10712 </listitem>
10713
10714 <!--
10715 Author: Peter Eisentraut <[email protected]>
10716 2025-01-11 [ca87c415e] Add support for NOT ENFORCED in CHECK constraints
10717 Author: Peter Eisentraut <[email protected]>
10718 2025-04-02 [eec0040c4] Add support for NOT ENFORCED in foreign key constraints
10719 -->
10720
10721 <listitem>
10722 <para>
10723 Allow <link
10724 linkend="sql-createtable-parms-check"><literal>CHECK</literal></link>
10725 and <link linkend="sql-createtable-parms-references">foreign
10726 key</link> constraints to be specified as <literal>NOT
10727 ENFORCED</literal> (Amul Sul)
10728 <ulink url="&commit_baseurl;ca87c415e">&sect;</ulink>
10729 <ulink url="&commit_baseurl;eec0040c4">&sect;</ulink>
10730 </para>
10731
10732 <para>
10733 This also adds column <link
10734 linkend="catalog-pg-constraint"><structname>pg_constraint</structname></link>.<structfield>conenforced</structfield>.
10735 </para>
10736 </listitem>
10737
10738 <!--
10739 Author: Peter Eisentraut <[email protected]>
10740 2024-11-15 [9321d2fdf] Fix collation handling for foreign keys
10741 -->
10742
10743 <listitem>
10744 <para>
10745 Require <link
10746 linkend="sql-createtable-parms-references">primary/foreign key</link>
10747 relationships to use either deterministic collations or the the
10748 same nondeterministic collations (Peter Eisentraut)
10749 <ulink url="&commit_baseurl;9321d2fdf">&sect;</ulink>
10750 </para>
10751
10752 <para>
10753 The restore of a <xref linkend="app-pgdump"/>, also used by <xref
10754 linkend="pgupgrade"/>, will fail if these requirements are not met;
10755 schema changes must be made for these upgrade methods to succeed.
10756 </para>
10757 </listitem>
10758
10759 <!--
10760 Author: Álvaro Herrera <[email protected]>
10761 2024-11-08 [14e87ffa5] Add pg_constraint rows for not-null constraints
10762 Author: Fujii Masao <[email protected]>
10763 Branch: master Release: REL_18_BR [81ce602d4] 2025-06-26 20:25:34 +0900
10764 -->
10765
10766 <listitem>
10767 <para>
10768 Store column <link
10769 linkend="sql-createtable-parms-not-null"><literal>NOT
10770 NULL</literal></link> specifications in <link
10771 linkend="catalog-pg-constraint"><structname>pg_constraint</structname></link>
10772 (Álvaro Herrera, Bernd Helmle)
10773 <ulink url="&commit_baseurl;14e87ffa5">&sect;</ulink>
10774 <ulink url="&commit_baseurl;81ce602d4">&sect;</ulink>
10775 </para>
10776
10777 <para>
10778 This allows names to be specified for <literal>NOT NULL</literal>
10779 constraint. This also adds <literal>NOT NULL</literal> constraints
10780 to foreign tables and <literal>NOT NULL</literal> inheritance
10781 control to local tables.
10782 </para>
10783 </listitem>
10784
10785 <!--
10786 Author: Álvaro Herrera <[email protected]>
10787 2025-04-07 [a379061a2] Allow NOT NULL constraints to be added as NOT VALID
10788 -->
10789
10790 <listitem>
10791 <para>
10792 Allow <xref linkend="sql-altertable"/> to set the <literal>NOT
10793 VALID</literal> attribute of <literal>NOT NULL</literal> constraints
10794 (Rushabh Lathia, Jian He)
10795 <ulink url="&commit_baseurl;a379061a2">&sect;</ulink>
10796 </para>
10797 </listitem>
10798
10799 <!--
10800 Author: Álvaro Herrera <[email protected]>
10801 2025-03-05 [f4e53e10b] Add ALTER TABLE ... ALTER CONSTRAINT ... SET [NO] INHERI
10802 Author: Álvaro Herrera <[email protected]>
10803 2025-03-27 [4a02af8b1] Simplify syntax for ALTER TABLE ALTER CONSTRAINT NO INHE
10804 -->
10805
10806 <listitem>
10807 <para>
10808 Allow modification of the inheritability of <literal>NOT
10809 NULL</literal> constraints (Suraj Kharage, Álvaro Herrera)
10810 <ulink url="&commit_baseurl;f4e53e10b">&sect;</ulink>
10811 <ulink url="&commit_baseurl;4a02af8b1">&sect;</ulink>
10812 </para>
10813
10814 <para>
10815 The syntax is <link linkend="sql-altertable"><command>ALTER TABLE
10816 ... ALTER CONSTRAINT ... [NO] INHERIT</command></link>.
10817 </para>
10818 </listitem>
10819
10820 <!--
10821 Author: Álvaro Herrera <[email protected]>
10822 2025-01-23 [b663b9436] Allow NOT VALID foreign key constraints on partitioned t
10823 -->
10824
10825 <listitem>
10826 <para>
10827 Allow <literal>NOT VALID</literal> foreign key constraints on
10828 partitioned tables (Amul Sul)
10829 <ulink url="&commit_baseurl;b663b9436">&sect;</ulink>
10830 </para>
10831 </listitem>
10832
10833 <!--
10834 Author: Álvaro Herrera <[email protected]>
10835 2024-09-30 [4dea33ce7] Don't disallow DROP of constraints ONLY on partitioned t
10836 -->
10837
10838 <listitem>
10839 <para>
10840 Allow <link
10841 linkend="sql-altertable-desc-drop-constraint">dropping</link>
10842 of constraints <literal>ONLY</literal> on partitioned tables
10843 (Álvaro Herrera)
10844 <ulink url="&commit_baseurl;4dea33ce7">&sect;</ulink>
10845 </para>
10846
10847 <para>
10848 This was previously erroneously prohibited.
10849 </para>
10850 </listitem>
10851
10852 </itemizedlist>
10853 </sect4>
10854
10855 <sect4 id="release-18-copy">
10856 <title><xref linkend="sql-copy"/></title>
10857
10858 <itemizedlist>
10859
10860 <!--
10861 Author: Fujii Masao <[email protected]>
10862 2024-10-08 [4ac2a9bec] Add REJECT_LIMIT option to the COPY command.
10863 -->
10864
10865 <listitem>
10866 <para>
10867 Add <literal>REJECT_LIMIT</literal> to control the number of invalid
10868 rows <command>COPY FROM</command> can ignore (Atsushi Torikoshi)
10869 <ulink url="&commit_baseurl;4ac2a9bec">&sect;</ulink>
10870 </para>
10871
10872 <para>
10873 This is available when <literal>ON_ERROR = 'ignore'</literal>.
10874 </para>
10875 </listitem>
10876
10877 <!--
10878 Author: Fujii Masao <[email protected]>
10879 2025-04-04 [534874fac] Allow "COPY table TO" command to copy rows from material
10880 -->
10881
10882 <listitem>
10883 <para>
10884 Allow <command>COPY TO</command> to copy rows from populated
10885 materialized views (Jian He)
10886 <ulink url="&commit_baseurl;534874fac">&sect;</ulink>
10887 </para>
10888 </listitem>
10889
10890 <!--
10891 Author: Fujii Masao <[email protected]>
10892 2024-10-03 [e7834a1a2] Add LOG_VERBOSITY = 'silent' support to COPY command.
10893 -->
10894
10895 <listitem>
10896 <para>
10897 Add <command>COPY</command> <literal>LOG_VERBOSITY</literal> level
10898 <literal>silent</literal> to suppress log output of ignored rows
10899 (Atsushi Torikoshi)
10900 <ulink url="&commit_baseurl;e7834a1a2">&sect;</ulink>
10901 </para>
10902
10903 <para>
10904 This new level suppresses output for discarded input rows when
10905 <literal>on_error = 'ignore'</literal>.
10906 </para>
10907 </listitem>
10908
10909 <!--
10910 Author: Nathan Bossart <[email protected]>
10911 2025-02-06 [401a6956f] Disallow COPY FREEZE on foreign tables.
10912 -->
10913
10914 <listitem>
10915 <para>
10916 Disallow <command>COPY FREEZE</command> on foreign tables (Nathan
10917 Bossart)
10918 <ulink url="&commit_baseurl;401a6956f">&sect;</ulink>
10919 </para>
10920
10921 <para>
10922 Previously, the <command>COPY</command> worked but the
10923 <literal>FREEZE</literal> was ignored, so disallow this command.
10924 </para>
10925 </listitem>
10926
10927 </itemizedlist>
10928 </sect4>
10929
10930 <sect4 id="release-18-explain">
10931 <title><xref linkend="sql-explain"/></title>
10932
10933 <itemizedlist>
10934
10935 <!--
10936 Author: David Rowley <[email protected]>
10937 2024-12-11 [c2a4078eb] Enable BUFFERS with EXPLAIN ANALYZE by default
10938 -->
10939
10940 <listitem>
10941 <para>
10942 Automatically include <literal>BUFFERS</literal> output in
10943 <command>EXPLAIN ANALYZE</command> (Guillaume Lelarge, David Rowley)
10944 <ulink url="&commit_baseurl;c2a4078eb">&sect;</ulink>
10945 </para>
10946 </listitem>
10947
10948 <!--
10949 Author: Michael Paquier <[email protected]>
10950 2025-02-17 [320545bfc] Add information about WAL buffers being full to EXPLAIN
10951 -->
10952
10953 <listitem>
10954 <para>
10955 Add full <acronym>WAL</acronym> buffer count to <command>EXPLAIN
10956 (WAL)</command> output (Bertrand Drouvot)
10957 <ulink url="&commit_baseurl;320545bfc">&sect;</ulink>
10958 </para>
10959 </listitem>
10960
10961 <!--
10962 Author: Peter Geoghegan <[email protected]>
10963 2025-03-11 [0fbceae84] Show index search count in EXPLAIN ANALYZE, take 2.
10964 -->
10965
10966 <listitem>
10967 <para>
10968 In <command>EXPLAIN ANALYZE</command>, report the number of index
10969 lookups used per index scan node (Peter Geoghegan)
10970 <ulink url="&commit_baseurl;0fbceae84">&sect;</ulink>
10971 </para>
10972 </listitem>
10973
10974 <!--
10975 Author: Robert Haas <[email protected]>
10976 2025-02-21 [ddb17e387] Allow EXPLAIN to indicate fractional rows.
10977 Author: Robert Haas <[email protected]>
10978 2025-02-27 [95dbd827f] EXPLAIN: Always use two fractional digits for row counts
10979 -->
10980
10981 <listitem>
10982 <para>
10983 Modify <command>EXPLAIN</command> to output fractional row counts
10984 (Ibrar Ahmed, Ilia Evdokimov, Robert Haas)
10985 <ulink url="&commit_baseurl;ddb17e387">&sect;</ulink>
10986 <ulink url="&commit_baseurl;95dbd827f">&sect;</ulink>
10987 </para>
10988 </listitem>
10989
10990 <!--
10991 Author: David Rowley <[email protected]>
10992 2024-07-05 [1eff8279d] Add memory/disk usage for Material nodes in EXPLAIN
10993 Author: David Rowley <[email protected]>
10994 2024-07-05 [53abb1e0e] Fix newly introduced issue in EXPLAIN for Materialize no
10995 Author: Tatsuo Ishii <[email protected]>
10996 2024-09-17 [95d6e9af0] Add memory/disk usage for Window aggregate nodes in EXPL
10997 Author: Tatsuo Ishii <[email protected]>
10998 2024-09-23 [40708acd6] Add memory/disk usage for more executor nodes.
10999 -->
11000
11001 <listitem>
11002 <para>
11003 Add memory and disk usage details to <literal>Material</literal>,
11004 <literal>Window Aggregate</literal>, and common table expression
11005 nodes to <command>EXPLAIN</command> output (David Rowley, Tatsuo
11006 Ishii)
11007 <ulink url="&commit_baseurl;1eff8279d">&sect;</ulink>
11008 <ulink url="&commit_baseurl;53abb1e0e">&sect;</ulink>
11009 <ulink url="&commit_baseurl;95d6e9af0">&sect;</ulink>
11010 <ulink url="&commit_baseurl;40708acd6">&sect;</ulink>
11011 </para>
11012 </listitem>
11013
11014
11015 <!--
11016 Author: Tom Lane <[email protected]>
11017 2025-03-11 [8b1b34254] Improve EXPLAIN's display of window functions.
11018 -->
11019
11020 <listitem>
11021 <para>
11022 Add details about window function arguments to
11023 <command>EXPLAIN</command> output (Tom Lane)
11024 <ulink url="&commit_baseurl;8b1b34254">&sect;</ulink>
11025 </para>
11026 </listitem>
11027
11028 <!--
11029 Author: David Rowley <[email protected]>
11030 2024-07-09 [5a1e6df3b] Show Parallel Bitmap Heap Scan worker stats in EXPLAIN A
11031 -->
11032
11033 <listitem>
11034 <para>
11035 Add <literal>Parallel Bitmap Heap Scan</literal> worker cache
11036 statistics to <command>EXPLAIN ANALYZE</command> (David Geier,
11037 Heikki Linnakangas, Donghang Lin, Alena Rybakina, David Rowley)
11038 <ulink url="&commit_baseurl;5a1e6df3b">&sect;</ulink>
11039 </para>
11040 </listitem>
11041
11042 <!--
11043 Author: Robert Haas <[email protected]>
11044 2024-08-21 [c01743aa4] Show number of disabled nodes in EXPLAIN ANALYZE output.
11045 Author: David Rowley <[email protected]>
11046 2024-10-11 [161320b4b] Adjust EXPLAIN's output for disabled nodes
11047 Author: David Rowley <[email protected]>
11048 2024-10-29 [84b8fccbe] Doc: add detail about EXPLAIN's "Disabled" property
11049 -->
11050
11051 <listitem>
11052 <para>
11053 Indicate disabled nodes in <command>EXPLAIN ANALYZE</command> output
11054 (Robert Haas, David Rowley, Laurenz Albe)
11055 <ulink url="&commit_baseurl;c01743aa4">&sect;</ulink>
11056 <ulink url="&commit_baseurl;161320b4b">&sect;</ulink>
11057 <ulink url="&commit_baseurl;84b8fccbe">&sect;</ulink>
11058 </para>
11059 </listitem>
11060
11061 </itemizedlist>
11062
11063 </sect4>
11064
11065 </sect3>
11066
11067 <sect3 id="release-18-datatypes">
11068 <title>Data Types</title>
11069
11070 <itemizedlist>
11071
11072 <!--
11073 Author: Jeff Davis <[email protected]>
11074 2025-01-23 [4e7f62bc3] Add support for Unicode case folding.
11075 Author: Jeff Davis <[email protected]>
11076 2025-01-17 [286a365b9] Support Unicode full case mapping and conversion.
11077 -->
11078
11079 <listitem>
11080 <para>
11081 Improve <link linkend="collation-managing-standard">Unicode</link>
11082 full case mapping and conversion (Jeff Davis)
11083 <ulink url="&commit_baseurl;4e7f62bc3">&sect;</ulink>
11084 <ulink url="&commit_baseurl;286a365b9">&sect;</ulink>
11085 </para>
11086
11087 <para>
11088 This adds the ability to do conditional and title case mapping,
11089 and case map single characters to multiple characters.
11090 </para>
11091 </listitem>
11092
11093 <!--
11094 Author: Tom Lane <[email protected]>
11095 2025-01-24 [a5579a90a] Make jsonb casts to scalar types translate JSON null to
11096 -->
11097
11098 <listitem>
11099 <para>
11100 Allow <link linkend="datatype-json"><type>jsonb</type></link>
11101 <literal>null</literal> values to be cast to scalar types as
11102 <literal>NULL</literal> (Tom Lane)
11103 <ulink url="&commit_baseurl;a5579a90a">&sect;</ulink>
11104 </para>
11105
11106 <para>
11107 Previously such casts generated an error.
11108 </para>
11109 </listitem>
11110
11111 <!--
11112 Author: Andrew Dunstan <[email protected]>
11113 2025-03-05 [4603903d2] Allow json{b}_strip_nulls() to remove null array elements
11114 -->
11115
11116 <listitem>
11117 <para>
11118 Add optional parameter to <link
11119 linkend="functions-json-processing-table"><function>json{b}_strip_nulls</function></link>
11120 to allow removal of null array elements (Florents Tselai)
11121 <ulink url="&commit_baseurl;4603903d2">&sect;</ulink>
11122 </para>
11123 </listitem>
11124
11125 <!--
11126 Author: Tom Lane <[email protected]>
11127 2025-04-01 [6c12ae09f] Introduce a SQL-callable function array_sort(anyarray).
11128 -->
11129
11130 <listitem>
11131 <para>
11132 Add function <link
11133 linkend="array-functions-table"><function>array_sort()</function></link>
11134 which sorts an array's first dimension (Junwang Zhao, Jian He)
11135 <ulink url="&commit_baseurl;6c12ae09f">&sect;</ulink>
11136 </para>
11137 </listitem>
11138
11139 <!--
11140 Author: Michael Paquier <[email protected]>
11141 2024-11-01 [49d6c7d8d] Add SQL function array_reverse()
11142 -->
11143
11144 <listitem>
11145 <para>
11146 Add function <link
11147 linkend="array-functions-table"><function>array_reverse()</function></link>
11148 which reverses an array's first dimension (Aleksander Alekseev)
11149 <ulink url="&commit_baseurl;49d6c7d8d">&sect;</ulink>
11150 </para>
11151 </listitem>
11152
11153 <!--
11154 Author: Nathan Bossart <[email protected]>
11155 2025-03-13 [0697b2390] Add reverse(bytea).
11156 -->
11157
11158 <listitem>
11159 <para>
11160 Add function <link
11161 linkend="functions-string-other"><function>reverse()</function></link>
11162 to reverse bytea bytes (Aleksander Alekseev)
11163 <ulink url="&commit_baseurl;0697b2390">&sect;</ulink>
11164 </para>
11165 </listitem>
11166
11167 <!--
11168 Author: Dean Rasheed <[email protected]>
11169 2025-03-07 [6da469bad] Allow casting between bytea and integer types.
11170 -->
11171
11172 <listitem>
11173 <para>
11174 Allow casting between integer types and <link
11175 linkend="datatype-binary"><type>bytea</type></link> (Aleksander
11176 Alekseev)
11177 <ulink url="&commit_baseurl;6da469bad">&sect;</ulink>
11178 </para>
11179
11180 <para>
11181 The integer values are stored as <type>bytea</type> two's complement
11182 values.
11183 </para>
11184 </listitem>
11185
11186 <!--
11187 Author: Peter Eisentraut <[email protected]>
11188 2025-04-03 [82a46cca9] Update Unicode data to Unicode 16.0.0
11189 -->
11190
11191 <listitem>
11192 <para>
11193 Update Unicode data to <link
11194 linkend="collation-managing-standard">Unicode</link> 16.0.0 (Peter
11195 Eisentraut)
11196 <ulink url="&commit_baseurl;82a46cca9">&sect;</ulink>
11197 </para>
11198 </listitem>
11199
11200 <!--
11201 Author: Tom Lane <[email protected]>
11202 2025-02-18 [b464e51ab] Update to latest Snowball sources.
11203 -->
11204
11205 <listitem>
11206 <para>
11207 Add full text search <link
11208 linkend="textsearch-snowball-dictionary">stemming</link> for Estonian
11209 (Tom Lane)
11210 <ulink url="&commit_baseurl;b464e51ab">&sect;</ulink>
11211 </para>
11212 </listitem>
11213
11214 <!--
11215 Author: Tom Lane <[email protected]>
11216 2024-09-24 [cd838e200] Neaten up our choices of SQLSTATEs for XML-related error
11217 -->
11218
11219 <listitem>
11220 <para>
11221 Improve the <link linkend="datatype-xml"><type>XML</type></link>
11222 error codes to more closely match the <acronym>SQL</acronym> standard
11223 (Tom Lane)
11224 <ulink url="&commit_baseurl;cd838e200">&sect;</ulink>
11225 </para>
11226
11227 <para>
11228 These errors are reported via <link
11229 linkend="errcodes-appendix"><literal>SQLSTATE</literal></link>.
11230 </para>
11231 </listitem>
11232
11233 </itemizedlist>
11234
11235 </sect3>
11236
11237 <sect3 id="release-18-functions">
11238 <title>Functions</title>
11239
11240 <itemizedlist>
11241
11242 <!--
11243 Author: Jeff Davis <[email protected]>
11244 2025-01-24 [bfc599206] Add SQL function CASEFOLD().
11245 -->
11246
11247 <listitem>
11248 <para>
11249 Add function <link
11250 linkend="functions-string-other"><function>casefold()</function></link>
11251 to allow for more sophisticated case-insensitive matching (Jeff Davis)
11252 <ulink url="&commit_baseurl;bfc599206">&sect;</ulink>
11253 </para>
11254
11255 <para>
11256 This allows more accurate comparisons, i.e., a character can have
11257 multiple upper or lower case equivalents, or upper or lower case
11258 conversion changes the number of characters.
11259 </para>
11260 </listitem>
11261
11262 <!--
11263 Author: Tom Lane <[email protected]>
11264 2024-07-11 [a0f1fce80] Add min and max aggregates for composite types (records)
11265 Author: Tom Lane <[email protected]>
11266 2024-10-08 [2d24fd942] Add min and max aggregates for bytea type.
11267 -->
11268
11269 <listitem>
11270 <para>
11271 Allow <link
11272 linkend="functions-aggregate-table"><function>MIN()</function></link>/<link
11273 linkend="functions-aggregate-table"><function>MAX()</function></link>
11274 aggregates on arrays and composite types (Aleksander Alekseev,
11275 Marat Buharov)
11276 <ulink url="&commit_baseurl;a0f1fce80">&sect;</ulink>
11277 <ulink url="&commit_baseurl;2d24fd942">&sect;</ulink>
11278 </para>
11279 </listitem>
11280
11281 <!--
11282 Author: Tom Lane <[email protected]>
11283 2024-08-16 [6be39d77a] Fix extraction of week and quarter fields from intervals
11284 -->
11285
11286 <listitem>
11287 <para>
11288 Add a <literal>WEEK</literal> option to <link
11289 linkend="functions-datetime-extract"><function>EXTRACT()</function></link>
11290 (Tom Lane)
11291 <ulink url="&commit_baseurl;6be39d77a">&sect;</ulink>
11292 </para>
11293 </listitem>
11294
11295 <!--
11296 Author: Tom Lane <[email protected]>
11297 2024-08-16 [6be39d77a] Fix extraction of week and quarter fields from intervals
11298 -->
11299
11300 <listitem>
11301 <para>
11302 Improve the output <literal>EXTRACT(QUARTER ...)</literal> for
11303 negative values (Tom Lane)
11304 <ulink url="&commit_baseurl;6be39d77a">&sect;</ulink>
11305 </para>
11306 </listitem>
11307
11308 <!--
11309 Author: Tom Lane <[email protected]>
11310 2025-01-22 [172e6b3ad] Support RN (roman-numeral format) in to_number().
11311 -->
11312
11313 <listitem>
11314 <para>
11315 Add roman numeral support to <link
11316 linkend="functions-formatting-table"><function>to_number()</function></link>
11317 (Hunaid Sohail)
11318 <ulink url="&commit_baseurl;172e6b3ad">&sect;</ulink>
11319 </para>
11320
11321 <para>
11322 This is accessed via the <literal>RN</literal> pattern.
11323 </para>
11324 </listitem>
11325
11326 <!--
11327 Author: Masahiko Sawada <[email protected]>
11328 2024-12-11 [78c5e141e] Add UUID version 7 generation function.
11329 -->
11330
11331 <listitem>
11332 <para>
11333 Add <link linkend="datatype-uuid"><type>UUID</type></link>
11334 version 7 generation function <link
11335 linkend="func_uuid_gen_table"><function>uuidv7()</function></link>
11336 (Andrey Borodin)
11337 <ulink url="&commit_baseurl;78c5e141e">&sect;</ulink>
11338 </para>
11339
11340 <para>
11341 This <type>UUID</type> value is
11342 temporally sortable. Function alias <link
11343 linkend="func_uuid_gen_table"><function>uuidv4()</function></link>
11344 has been added to explicitly generate version 4 UUIDs.
11345 </para>
11346 </listitem>
11347
11348 <!--
11349 Author: Nathan Bossart <[email protected]>
11350 2024-08-12 [760162fed] Add user-callable CRC functions.
11351 -->
11352
11353 <listitem>
11354 <para>
11355 Add functions <link
11356 linkend="functions-binarystring-other"><function>crc32()</function></link>
11357 and <link
11358 linkend="functions-binarystring-other"><function>crc32c()</function></link>
11359 to compute <acronym>CRC</acronym> values (Aleksander Alekseev)
11360 <ulink url="&commit_baseurl;760162fed">&sect;</ulink>
11361 </para>
11362 </listitem>
11363
11364 <!--
11365 Author: Dean Rasheed <[email protected]>
11366 2025-03-26 [a3b6dfd41] Add support for gamma() and lgamma() functions.
11367 -->
11368
11369 <listitem>
11370 <para>
11371 Add math functions <link
11372 linkend="functions-math-func-table"><function>gamma()</function></link>
11373 and <link
11374 linkend="functions-math-func-table"><function>lgamma()</function></link>
11375 (Dean Rasheed)
11376 <ulink url="&commit_baseurl;a3b6dfd41">&sect;</ulink>
11377 </para>
11378 </listitem>
11379
11380 <!--
11381 Author: Tom Lane <[email protected]>
11382 2025-03-03 [246dedc5d] Allow =&gt; syntax for named cursor arguments in plpgsql.
11383 -->
11384
11385 <listitem>
11386 <para>
11387 Allow <literal>=&gt;</literal> syntax for named cursor arguments in
11388 <link linkend="plpgsql">PL/pgSQL</link> (Pavel Stehule)
11389 <ulink url="&commit_baseurl;246dedc5d">&sect;</ulink>
11390 </para>
11391
11392 <para>
11393 We previously only accepted <literal>:=</literal>.
11394 </para>
11395 </listitem>
11396
11397 <!--
11398 Author: Tom Lane <[email protected]>
11399 2024-07-25 [580f8727c] Add argument names to the regexp_XXX functions.
11400 -->
11401
11402 <listitem>
11403 <para>
11404 Allow <link
11405 linkend="functions-posix-regexp"><function>regexp_match[es]()</function></link>/<link
11406 linkend="functions-posix-regexp"><function>regexp_like()</function></link>/<link
11407 linkend="functions-posix-regexp"><function>regexp_replace()</function></link>/<link
11408 linkend="functions-posix-regexp"><function>regexp_count()</function></link>/<link
11409 linkend="functions-posix-regexp"><function>regexp_instr()</function></link>/<link
11410 linkend="functions-posix-regexp"><function>regexp_substr()</function></link>/<link
11411 linkend="functions-posix-regexp"><function>regexp_split_to_table()</function></link>/<link
11412 linkend="functions-posix-regexp"><function>regexp_split_to_array()</function></link>
11413 to use named arguments (Jian He)
11414 <ulink url="&commit_baseurl;580f8727c">&sect;</ulink>
11415 </para>
11416 </listitem>
11417
11418 </itemizedlist>
11419
11420 </sect3>
11421
11422 <sect3 id="release-18-libpq">
11423 <title><link linkend="libpq">Libpq</link></title>
11424
11425 <itemizedlist>
11426
11427 <!--
11428 Author: Robert Haas <[email protected]>
11429 2024-09-09 [cdb6b0fdb] Add PQfullProtocolVersion() to surface the precise proto
11430 -->
11431
11432 <listitem>
11433 <para>
11434 Add function <link
11435 linkend="libpq-PQfullProtocolVersion"><function>PQfullProtocolVersion()</function></link>
11436 to report the full, including minor, protocol version number (Jacob
11437 Champion, Jelte Fennema-Nio)
11438 <ulink url="&commit_baseurl;cdb6b0fdb">&sect;</ulink>
11439 </para>
11440 </listitem>
11441
11442 <!--
11443 Author: Heikki Linnakangas <[email protected]>
11444 2025-04-02 [285613c60] libpq: Add min/max_protocol_version connection options
11445 Author: Heikki Linnakangas <[email protected]>
11446 2025-04-02 [507034910] libpq: Handle NegotiateProtocolVersion message different
11447 -->
11448
11449 <listitem>
11450 <para>
11451 Add libpq connection <link
11452 linkend="libpq-connect-ssl-max-protocol-version">parameters</link>
11453 and <link linkend="libpq-envars">environment variables</link> to
11454 specify the minimum and maximum acceptable protocol version for
11455 connections (Jelte Fennema-Nio)
11456 <ulink url="&commit_baseurl;285613c60">&sect;</ulink>
11457 <ulink url="&commit_baseurl;507034910">&sect;</ulink>
11458 </para>
11459 </listitem>
11460
11461 <!--
11462 Author: Tomas Vondra <[email protected]>
11463 2024-08-19 [28a1121fd] Mark search_path as GUC_REPORT
11464 Author: Tomas Vondra <[email protected]>
11465 2024-08-19 [0d06a7eac] Document that search_path is reported by the server
11466 -->
11467
11468 <listitem>
11469 <para>
11470 Report <xref linkend="guc-search-path"/> changes to the client
11471 (Alexander Kukushkin, Jelte Fennema-Nio, Tomas Vondra)
11472 <ulink url="&commit_baseurl;28a1121fd">&sect;</ulink>
11473 <ulink url="&commit_baseurl;0d06a7eac">&sect;</ulink>
11474 </para>
11475 </listitem>
11476
11477 <!--
11478 Author: Álvaro Herrera <[email protected]>
11479 2024-08-12 [ea92f3a0a] libpq: Trace frontend authentication challenges
11480 Author: Álvaro Herrera <[email protected]>
11481 2024-08-14 [a5c6b8f22] libpq: Trace responses to SSLRequest and GSSENCRequest
11482 Author: Álvaro Herrera <[email protected]>
11483 2024-08-16 [b8b3f861f] libpq: Trace all messages received from the server
11484 Author: Robert Haas <[email protected]>
11485 2025-02-24 [e87c14b19] libpq: Trace all NegotiateProtocolVersion fields
11486 Author: Álvaro Herrera <[email protected]>
11487 2024-08-09 [7adec2d5f] libpq: Trace StartupMessage/SSLRequest/GSSENCRequest cor
11488 -->
11489
11490 <listitem>
11491 <para>
11492 Add <link
11493 linkend="libpq-PQtrace"><function>PQtrace()</function></link> output
11494 for all message types, including authentication (Jelte Fennema-Nio)
11495 <ulink url="&commit_baseurl;ea92f3a0a">&sect;</ulink>
11496 <ulink url="&commit_baseurl;a5c6b8f22">&sect;</ulink>
11497 <ulink url="&commit_baseurl;b8b3f861f">&sect;</ulink>
11498 <ulink url="&commit_baseurl;e87c14b19">&sect;</ulink>
11499 <ulink url="&commit_baseurl;7adec2d5f">&sect;</ulink>
11500 </para>
11501 </listitem>
11502
11503 <!--
11504 Author: Daniel Gustafsson <[email protected]>
11505 2025-04-03 [2da74d8d6] libpq: Add support for dumping SSL key material to file
11506 -->
11507
11508 <listitem>
11509 <para>
11510 Add libpq connection parameter <link
11511 linkend="libpq-connect-sslkeylogfile"><varname>sslkeylogfile</varname></link>
11512 which dumps out <acronym>SSL</acronym> key material (Abhishek Chanda,
11513 Daniel Gustafsson)
11514 <ulink url="&commit_baseurl;2da74d8d6">&sect;</ulink>
11515 </para>
11516
11517 <para>
11518 This is useful for debugging.
11519 </para>
11520 </listitem>
11521
11522 <!--
11523 Author: Thomas Munro <[email protected]>
11524 2025-03-25 [3c86223c9] libpq: Deprecate pg_int64.
11525 -->
11526
11527 <listitem>
11528 <para>
11529 Modify some libpq function signatures to use
11530 <literal>int64_t</literal> (Thomas Munro)
11531 <ulink url="&commit_baseurl;3c86223c9">&sect;</ulink>
11532 </para>
11533
11534 <para>
11535 These previously used <literal>pg_int64</literal>, which is now
11536 deprecated.
11537 </para>
11538 </listitem>
11539
11540 </itemizedlist>
11541
11542 </sect3>
11543
11544 <sect3 id="release-18-psql">
11545 <title><xref linkend="app-psql"/></title>
11546
11547 <itemizedlist>
11548
11549 <!--
11550 Author: Michael Paquier <[email protected]>
11551 2024-08-22 [d55322b0d] psql: Add more meta-commands able to use the extended pr
11552 Author: Michael Paquier <[email protected]>
11553 Branch: master Release: REL_18_BR [fc39b286a] 2025-06-24 13:12:46 +0900
11554 -->
11555
11556 <listitem>
11557 <para>
11558 Allow <application>psql</application> to parse, bind, and close
11559 named prepared statements (Anthonin Bonnefoy, Michael Paquier)
11560 <ulink url="&commit_baseurl;d55322b0d">&sect;</ulink>
11561 <ulink url="&commit_baseurl;fc39b286a">&sect;</ulink>
11562 </para>
11563
11564 <para>
11565 This is accomplished with new commands <link
11566 linkend="app-psql-meta-command-parse"><literal>\parse</literal></link>,
11567 <link
11568 linkend="app-psql-meta-command-bind-named"><literal>\bind_named</literal></link>,
11569 and <link
11570 linkend="app-psql-meta-command-close-prepared"><literal>\close_prepared</literal></link>.
11571 </para>
11572 </listitem>
11573
11574 <!--
11575 Author: Michael Paquier <[email protected]>
11576 2025-02-21 [41625ab8e] psql: Add support for pipelines
11577 Author: Michael Paquier <[email protected]>
11578 2025-03-18 [17caf6644] psql: Add \sendpipeline to send query buffers while in a
11579 Author: Michael Paquier <[email protected]>
11580 2025-03-19 [2cce0fe44] psql: Allow queries terminated by semicolons while in pi
11581 -->
11582
11583 <listitem>
11584 <para>
11585 Add <application>psql</application> backslash commands to allowing
11586 issuance of pipeline queries (Anthonin Bonnefoy)
11587 <ulink url="&commit_baseurl;41625ab8e">&sect;</ulink>
11588 <ulink url="&commit_baseurl;17caf6644">&sect;</ulink>
11589 <ulink url="&commit_baseurl;2cce0fe44">&sect;</ulink>
11590 </para>
11591
11592 <para>
11593 The new commands are <link
11594 linkend="app-psql-meta-command-pipeline"><literal>\startpipeline</literal></link>,
11595 <literal>\syncpipeline</literal>, <literal>\sendpipeline</literal>,
11596 <literal>\endpipeline</literal>, <literal>\flushrequest</literal>,
11597 <literal>\flush</literal>, and <literal>\getresults</literal>.
11598 </para>
11599 </listitem>
11600
11601 <!--
11602 Author: Michael Paquier <[email protected]>
11603 2025-02-25 [3ce357584] psql: Add pipeline status to prompt and some state varia
11604 -->
11605
11606 <listitem>
11607 <para>
11608 Allow adding pipeline status to the <application>psql</application>
11609 prompt and add related state variables (Anthonin Bonnefoy)
11610 <ulink url="&commit_baseurl;3ce357584">&sect;</ulink>
11611 </para>
11612
11613 <para>
11614 The new prompt character is <literal>%P</literal> and
11615 the new <application>psql</application> variables are <link
11616 linkend="app-psql-variables-pipeline-sync-count"><literal>PIPELINE_SYNC_COUNT</literal></link>,
11617 <link
11618 linkend="app-psql-variables-pipeline-command-count"><literal>PIPELINE_COMMAND_COUNT</literal></link>,
11619 and <link
11620 linkend="app-psql-variables-pipeline-result-count"><literal>PIPELINE_RESULT_COUNT</literal></link>.
11621 </para>
11622 </listitem>
11623
11624 <!--
11625 Author: Michael Paquier <[email protected]>
11626 2024-12-18 [477728b5d] psql: Add more information about service name
11627 -->
11628
11629 <listitem>
11630 <para>
11631 Allow adding the connection service name to the
11632 <application>psql</application> prompt or access it via
11633 <application>psql</application> variable (Michael Banck)
11634 <ulink url="&commit_baseurl;477728b5d">&sect;</ulink>
11635 </para>
11636 </listitem>
11637
11638 <!--
11639 Author: Dean Rasheed <[email protected]>
11640 2025-01-14 [00f4c2959] psql: Add option to use expanded mode to all list comman
11641 -->
11642
11643 <listitem>
11644 <para>
11645 Add <application>psql</application> option to use expanded mode on
11646 all list commands (Dean Rasheed)
11647 <ulink url="&commit_baseurl;00f4c2959">&sect;</ulink>
11648 </para>
11649
11650 <para>
11651 Adding backslash suffix <literal>x</literal> enables this.
11652 </para>
11653 </listitem>
11654
11655 <!--
11656 Author: Álvaro Herrera <[email protected]>
11657 2025-02-22 [bba2fbc62] Change \conninfo to use tabular format
11658 -->
11659
11660 <listitem>
11661 <para>
11662 Change <application>psql</application>'s <xref
11663 linkend="app-psql-meta-command-conninfo"/> to use tabular format
11664 and include more information (Álvaro Herrera, Maiquel Grassi,
11665 Hunaid Sohail)
11666 <ulink url="&commit_baseurl;bba2fbc62">&sect;</ulink>
11667 </para>
11668 </listitem>
11669
11670 <!--
11671 Author: Dean Rasheed <[email protected]>
11672 2025-01-14 [2355e5111] psql: Add leakproof indicator to \df+, \do+, \dAo+, and
11673 -->
11674
11675 <listitem>
11676 <para>
11677 Add function's leakproof indicator
11678 to <application>psql</application>'s <link
11679 linkend="app-psql-meta-command-df-lc"><literal>\df+</literal></link>,
11680 <literal>\do+</literal>, <literal>\dAo+</literal>, and
11681 <literal>\dC+</literal> outputs (Yugo Nagata)
11682 <ulink url="&commit_baseurl;2355e5111">&sect;</ulink>
11683 </para>
11684 </listitem>
11685
11686 <!--
11687 Author: Michael Paquier <[email protected]>
11688 2024-07-02 [978f38c77] Add information about access method for partitioned rela
11689 -->
11690
11691 <listitem>
11692 <para>
11693 Add access method details for partitioned relations in <link
11694 linkend="app-psql-meta-command-dp-uc"><literal>\dP+</literal></link>
11695 (Justin Pryzby)
11696 <ulink url="&commit_baseurl;978f38c77">&sect;</ulink>
11697 </para>
11698 </listitem>
11699
11700 <!--
11701 Author: Magnus Hagander <[email protected]>
11702 2025-03-24 [d696406a9] psql: show default extension version in \dx output
11703 -->
11704
11705 <listitem>
11706 <para>
11707 Add <literal>default_version</literal>
11708 to the <application>psql</application> <link
11709 linkend="app-psql-meta-command-dx-lc"><literal>\dx</literal></link>
11710 extension output (Magnus Hagander)
11711 <ulink url="&commit_baseurl;d696406a9">&sect;</ulink>
11712 </para>
11713 </listitem>
11714
11715 <!--
11716 Author: Daniel Gustafsson <[email protected]>
11717 2025-03-25 [1a759c832] psql: Make default \watch interval configurable
11718 -->
11719
11720 <listitem>
11721 <para>
11722 Add <application>psql</application> variable <xref
11723 linkend="app-psql-variables-watch-interval"/> to set the default <link
11724 linkend="app-psql-meta-command-watch"><literal>\watch</literal></link>
11725 wait time (Daniel Gustafsson)
11726 <ulink url="&commit_baseurl;1a759c832">&sect;</ulink>
11727 </para>
11728 </listitem>
11729
11730 </itemizedlist>
11731
11732 </sect3>
11733
11734 <sect3 id="release-18-server-apps">
11735 <title>Server Applications</title>
11736
11737 <itemizedlist>
11738
11739 <!--
11740 Author: Peter Eisentraut <[email protected]>
11741 2024-10-01 [983a588e0] initdb: Add new option "- -no-data-checksums"
11742 Author: Peter Eisentraut <[email protected]>
11743 2024-10-16 [04bec894a] initdb: Change default to using data checksums.
11744 -->
11745
11746 <listitem>
11747 <para>
11748 Change <xref linkend="app-initdb"/> to default to enabling checksums
11749 (Greg Sabino Mullane)
11750 <ulink url="&commit_baseurl;983a588e0">&sect;</ulink>
11751 <ulink url="&commit_baseurl;04bec894a">&sect;</ulink>
11752 </para>
11753
11754 <para>
11755 The new <application>initdb</application> option
11756 <option>--no-data-checksums</option> disables checksums.
11757 </para>
11758 </listitem>
11759
11760 <!--
11761 Author: Nathan Bossart <[email protected]>
11762 2025-03-25 [cf131fa94] initdb: Add - -no-sync-data-files.
11763 -->
11764
11765 <listitem>
11766 <para>
11767 Add <application>initdb</application> option
11768 <option>--no-sync-data-files</option> to avoid syncing heap/index
11769 files (Nathan Bossart)
11770 <ulink url="&commit_baseurl;cf131fa94">&sect;</ulink>
11771 </para>
11772
11773 <para>
11774 <application>initdb</application> option <option>--no-sync</option>
11775 is still available to avoid syncing any files.
11776 </para>
11777 </listitem>
11778
11779 <!--
11780 Author: Nathan Bossart <[email protected]>
11781 2025-03-18 [edba754f0] vacuumdb: Add option for analyzing only relations missin
11782 Author: Nathan Bossart <[email protected]>
11783 2025-04-30 [987910502] vacuumdb: Don't skip empty relations in - -missing-stats-
11784 -->
11785
11786 <listitem>
11787 <para>
11788 Add <xref linkend="app-vacuumdb"/> option
11789 <option>--missing-stats-only</option> to compute only missing
11790 optimizer statistics (Corey Huinker, Nathan Bossart)
11791 <ulink url="&commit_baseurl;edba754f0">&sect;</ulink>
11792 <ulink url="&commit_baseurl;987910502">&sect;</ulink>
11793 </para>
11794
11795 <para>
11796 This option can only be run by superusers and can only
11797 be used with options <option>--analyze-only</option> and
11798 <option>--analyze-in-stages</option>.
11799 </para>
11800 </listitem>
11801
11802 <!--
11803 Author: Robert Haas <[email protected]>
11804 2025-03-17 [99aeb8470] pg_combinebackup: Add -k, - -link option.
11805 -->
11806
11807 <listitem>
11808 <para>
11809 Add <xref linkend="app-pgcombinebackup"/> option
11810 <option>-k</option>/<option>--link</option> to enable hard linking
11811 (Israel Barth Rubio, Robert Haas)
11812 <ulink url="&commit_baseurl;99aeb8470">&sect;</ulink>
11813 </para>
11814
11815 <para>
11816 Only some files can be hard linked. This should not be used if the
11817 backups will be used independently.
11818 </para>
11819 </listitem>
11820
11821 <!--
11822 Author: Robert Haas <[email protected]>
11823 2024-09-27 [8dfd31290] pg_verifybackup: Verify tar-format backups.
11824 -->
11825
11826 <listitem>
11827 <para>
11828 Allow <xref linkend="app-pgverifybackup"/> to verify tar-format
11829 backups (Amul Sul)
11830 <ulink url="&commit_baseurl;8dfd31290">&sect;</ulink>
11831 </para>
11832 </listitem>
11833
11834 <!--
11835 Author: Masahiko Sawada <[email protected]>
11836 2025-03-12 [4ecdd4110] pg_rewind: Add dbname to primary_conninfo when using - -w
11837 -->
11838
11839 <listitem>
11840 <para>
11841 If <xref linkend="app-pgrewind"/>'s <option>--source-server</option>
11842 specifies a database name, use it in
11843 <option>--write-recovery-conf</option> output (Masahiko Sawada)
11844 <ulink url="&commit_baseurl;4ecdd4110">&sect;</ulink>
11845 </para>
11846 </listitem>
11847
11848 <!--
11849 Author: Masahiko Sawada <[email protected]>
11850 2025-02-21 [30666d185] pg_resetwal: Add - -char-signedness option to change the
11851 -->
11852
11853 <listitem>
11854 <para>
11855 Add <xref linkend="app-pgresetwal"/> option
11856 <option>--char-signedness</option> to change the default
11857 <type>char</type> signedness (Masahiko Sawada)
11858 <ulink url="&commit_baseurl;30666d185">&sect;</ulink>
11859 </para>
11860 </listitem>
11861
11862 </itemizedlist>
11863
11864
11865 <sect4 id="release-18-pgdump">
11866 <title><link
11867 linkend="app-pgdump"><application>pg_dump</application></link>/<link
11868 linkend="app-pg-dumpall"><application>pg_dumpall</application></link>/<link
11869 linkend="app-pgrestore"><application>pg_restore</application></link></title>
11870
11871 <itemizedlist>
11872
11873 <!--
11874 Author: Jeff Davis <[email protected]>
11875 2025-03-25 [bde2fb797] Add pg_dump - -with-{schema|data|statistics} options.
11876 Author: Jeff Davis <[email protected]>
11877 2025-08-02 [a3e8dc143] Simplify options in pg_dump and pg_restore.
11878 -->
11879
11880 <listitem>
11881 <para>
11882 Add <xref linkend="app-pgdump"/> option <option>--statistics</option>
11883 (Jeff Davis)
11884 <ulink url="&commit_baseurl;bde2fb797">&sect;</ulink>
11885 <ulink url="&commit_baseurl;a3e8dc143">&sect;</ulink>
11886 </para>
11887 </listitem>
11888
11889 <!--
11890 Author: Nathan Bossart <[email protected]>
11891 2025-03-25 [9c49f0e8c] pg_dump: Add - -sequence-data.
11892 Author: Nathan Bossart <[email protected]>
11893 2025-05-07 [acea3fc49] pg_dumpall: Add - -sequence-data.
11894 -->
11895
11896 <listitem>
11897 <para>
11898 Add <application>pg_dump</application> and <xref
11899 linkend="app-pg-dumpall"/> option <option>--sequence-data</option> to
11900 dump sequence data that would normally be excluded (Nathan Bossart)
11901 <ulink url="&commit_baseurl;9c49f0e8c">&sect;</ulink>
11902 <ulink url="&commit_baseurl;acea3fc49">&sect;</ulink>
11903 </para>
11904 </listitem>
11905
11906 <!--
11907 Author: Jeff Davis <[email protected]>
11908 2025-02-20 [1fd1bd871] Transfer statistics during pg_upgrade.
11909 -->
11910
11911 <listitem>
11912 <para>
11913 Add <xref linkend="app-pgdump"/>, <xref linkend="app-pg-dumpall"/>,
11914 and <xref linkend="app-pgrestore"/> options
11915 <option>--statistics-only</option>, <option>--no-statistics</option>,
11916 <option>--no-data</option>, and <option>--no-schema</option>
11917 (Corey Huinker, Jeff Davis)
11918 <ulink url="&commit_baseurl;1fd1bd871">&sect;</ulink>
11919 </para>
11920 </listitem>
11921
11922 <!--
11923 Author: Tom Lane <[email protected]>
11924 2025-03-16 [cd3c45125] pg_dump, pg_dumpall, pg_restore: Add - -no-policies optio
11925 -->
11926
11927 <listitem>
11928 <para>
11929 Add option <option>--no-policies</option> to disable row level
11930 security policy processing in <xref linkend="app-pgdump"/>,
11931 <xref linkend="app-pg-dumpall"/>, <xref linkend="app-pgrestore"/>
11932 (Nikolay Samokhvalov)
11933 <ulink url="&commit_baseurl;cd3c45125">&sect;</ulink>
11934 </para>
11935
11936 <para>
11937 This is useful for migrating to systems with different policies.
11938 </para>
11939 </listitem>
11940
11941 </itemizedlist>
11942
11943 </sect4>
11944
11945 <sect4 id="release-18-pgupgrade">
11946 <title><xref linkend="pgupgrade"/></title>
11947
11948 <itemizedlist>
11949
11950 <!--
11951 Author: Jeff Davis <[email protected]>
11952 2025-02-20 [1fd1bd871] Transfer statistics during pg_upgrade.
11953 Author: Nathan Bossart <[email protected]>
11954 2025-03-18 [c9d502eb6] Update guidance for running vacuumdb after pg_upgrade.
11955 Author: Nathan Bossart <[email protected]>
11956 2025-04-30 [d5f1b6a75] Further adjust guidance for running vacuumdb after pg_up
11957 Author: Jeff Davis <[email protected]>
11958 2025-02-20 [1fd1bd871] Transfer statistics during pg_upgrade.
11959 -->
11960
11961 <listitem>
11962 <para>
11963 Allow <application>pg_upgrade</application> to preserve optimizer
11964 statistics (Corey Huinker, Jeff Davis, Nathan Bossart)
11965 <ulink url="&commit_baseurl;1fd1bd871">&sect;</ulink>
11966 <ulink url="&commit_baseurl;c9d502eb6">&sect;</ulink>
11967 <ulink url="&commit_baseurl;d5f1b6a75">&sect;</ulink>
11968 <ulink url="&commit_baseurl;1fd1bd871">&sect;</ulink>
11969 </para>
11970
11971 <para>
11972 Extended statistics are not preserved. Also add
11973 <application>pg_upgrade</application> option
11974 <option>--no-statistics</option> to disable statistics preservation.
11975 </para>
11976 </listitem>
11977
11978 <!--
11979 Author: Nathan Bossart <[email protected]>
11980 2024-09-16 [40e2e5e92] Introduce framework for parallelizing various pg_upgrade
11981 Author: Nathan Bossart <[email protected]>
11982 2024-09-16 [6d3d2e8e5] pg_upgrade: Parallelize retrieving relation information.
11983 Author: Nathan Bossart <[email protected]>
11984 2024-09-16 [7baa36de5] pg_upgrade: Parallelize subscription check.
11985 Author: Nathan Bossart <[email protected]>
11986 2024-09-16 [46cad8b31] pg_upgrade: Parallelize retrieving loadable libraries.
11987 Author: Nathan Bossart <[email protected]>
11988 2024-09-16 [6ab8f27bc] pg_upgrade: Parallelize retrieving extension updates.
11989 Author: Nathan Bossart <[email protected]>
11990 2024-09-16 [bbf83cab9] pg_upgrade: Parallelize data type checks.
11991 Author: Nathan Bossart <[email protected]>
11992 2024-09-16 [9db3018cf] pg_upgrade: Parallelize contrib/isn check.
11993 Author: Nathan Bossart <[email protected]>
11994 2024-09-16 [c34eabfbb] pg_upgrade: Parallelize postfix operator check.
11995 Author: Nathan Bossart <[email protected]>
11996 2024-09-16 [cf2f82a37] pg_upgrade: Parallelize incompatible polymorphics check.
11997 Author: Nathan Bossart <[email protected]>
11998 2024-09-16 [f93f5f7b9] pg_upgrade: Parallelize WITH OIDS check.
11999 Author: Nathan Bossart <[email protected]>
12000 2024-09-16 [c880cf258] pg_upgrade: Parallelize encoding conversion check.
12001 -->
12002
12003 <listitem>
12004 <para>
12005 Allow <application>pg_upgrade</application> to process database
12006 checks in parallel (Nathan Bossart)
12007 <ulink url="&commit_baseurl;40e2e5e92">&sect;</ulink>
12008 <ulink url="&commit_baseurl;6d3d2e8e5">&sect;</ulink>
12009 <ulink url="&commit_baseurl;7baa36de5">&sect;</ulink>
12010 <ulink url="&commit_baseurl;46cad8b31">&sect;</ulink>
12011 <ulink url="&commit_baseurl;6ab8f27bc">&sect;</ulink>
12012 <ulink url="&commit_baseurl;bbf83cab9">&sect;</ulink>
12013 <ulink url="&commit_baseurl;9db3018cf">&sect;</ulink>
12014 <ulink url="&commit_baseurl;c34eabfbb">&sect;</ulink>
12015 <ulink url="&commit_baseurl;cf2f82a37">&sect;</ulink>
12016 <ulink url="&commit_baseurl;f93f5f7b9">&sect;</ulink>
12017 <ulink url="&commit_baseurl;c880cf258">&sect;</ulink>
12018 </para>
12019
12020 <para>
12021 This is controlled by the existing <option>--jobs</option> option.
12022 </para>
12023 </listitem>
12024
12025 <!--
12026 Author: Nathan Bossart <[email protected]>
12027 2025-03-25 [626d7236b] pg_upgrade: Add - -swap for faster file transfer.
12028 -->
12029
12030 <listitem>
12031 <para>
12032 Add <application>pg_upgrade</application> option
12033 <option>--swap</option> to swap directories rather than copy, clone,
12034 or link files (Nathan Bossart)
12035 <ulink url="&commit_baseurl;626d7236b">&sect;</ulink>
12036 </para>
12037
12038 <para>
12039 This mode is potentially the fastest.
12040 </para>
12041 </listitem>
12042
12043 <!--
12044 Author: Masahiko Sawada <[email protected]>
12045 2025-02-21 [a8238f87f] pg_upgrade: Preserve default char signedness value from
12046 Author: Masahiko Sawada <[email protected]>
12047 2025-02-21 [1aab68059] pg_upgrade: Add - -set-char-signedness to set the default
12048 -->
12049
12050 <listitem>
12051 <para>
12052 Add <application>pg_upgrade</application> option
12053 <option>--set-char-signedness</option> to set the default
12054 <type>char</type> signedness of new cluster (Masahiko Sawada)
12055 <ulink url="&commit_baseurl;a8238f87f">&sect;</ulink>
12056 <ulink url="&commit_baseurl;1aab68059">&sect;</ulink>
12057 </para>
12058
12059 <para>
12060 This is to handle cases where a
12061 pre-<productname>PostgreSQL</productname> 18 cluster's default
12062 <acronym>CPU</acronym> signedness does not match the new cluster.
12063 </para>
12064 </listitem>
12065
12066 </itemizedlist>
12067
12068 </sect4>
12069
12070 <sect4 id="release-18-logicalrep-app">
12071 <title>Logical Replication Applications</title>
12072
12073 <itemizedlist>
12074
12075 <!--
12076 Author: Amit Kapila <[email protected]>
12077 2025-03-28 [fb2ea12f4] pg_createsubscriber: Add '- -all' option.
12078 -->
12079
12080 <listitem>
12081 <para>
12082 Add <xref linkend="app-pgcreatesubscriber"/> option
12083 <option>--all</option> to create logical replicas for all databases
12084 (Shubham Khanna)
12085 <ulink url="&commit_baseurl;fb2ea12f4">&sect;</ulink>
12086 </para>
12087 </listitem>
12088
12089 <!--
12090 Author: Amit Kapila <[email protected]>
12091 2025-03-20 [e5aeed4b8] pg_createsubscriber: Add -R publications option.
12092 Author: Peter Eisentraut <[email protected]>
12093 Branch: master Release: REL_18_BR [60dda7bbc] 2025-06-25 10:50:43 +0200
12094 -->
12095
12096 <listitem>
12097 <para>
12098 Add <application>pg_createsubscriber</application> option
12099 <option>--clean</option> to remove publications (Shubham Khanna)
12100 <ulink url="&commit_baseurl;e5aeed4b8">&sect;</ulink>
12101 <ulink url="&commit_baseurl;60dda7bbc">&sect;</ulink>
12102 </para>
12103 </listitem>
12104
12105 <!--
12106 Author: Amit Kapila <[email protected]>
12107 2025-02-26 [e117cfb2f] Add two-phase option in pg_createsubscriber.
12108 -->
12109
12110 <listitem>
12111 <para>
12112 Add <application>pg_createsubscriber</application> option
12113 <option>--enable-two-phase</option> to enable prepared transactions
12114 (Shubham Khanna)
12115 <ulink url="&commit_baseurl;e117cfb2f">&sect;</ulink>
12116 </para>
12117 </listitem>
12118
12119 <!--
12120 Author: Masahiko Sawada <[email protected]>
12121 2025-04-04 [cf2655a90] pg_recvlogical: Add - -failover option.
12122 -->
12123
12124 <listitem>
12125 <para>
12126 Add <xref linkend="app-pgrecvlogical"/> option
12127 <option>--enable-failover</option> to specify failover slots (Hayato Kuroda)
12128 <ulink url="&commit_baseurl;cf2655a90">&sect;</ulink>
12129 </para>
12130
12131 <para>
12132 Also add option <option>--enable-two-phase</option> as a synonym
12133 for <option>--two-phase</option>, and deprecate the latter.
12134 </para>
12135 </listitem>
12136
12137 <!--
12138 Author: Fujii Masao <[email protected]>
12139 2025-03-25 [c68100aa4] Allow pg_recvlogical - -drop-slot to work without - -dbnam
12140 -->
12141
12142 <listitem>
12143 <para>
12144 Allow <application>pg_recvlogical</application>
12145 <option>--drop-slot</option> to work without
12146 <option>--dbname</option> (Hayato Kuroda)
12147 <ulink url="&commit_baseurl;c68100aa4">&sect;</ulink>
12148 </para>
12149 </listitem>
12150
12151 </itemizedlist>
12152
12153 </sect4>
12154
12155 </sect3>
12156
12157 <sect3 id="release-18-source-code">
12158 <title>Source Code</title>
12159
12160 <itemizedlist>
12161
12162 <!--
12163 Author: Michael Paquier <[email protected]>
12164 2024-07-05 [4b211003e] Support loading of injection points
12165 Author: Michael Paquier <[email protected]>
12166 2024-07-18 [a0a5869a8] Add INJECTION_POINT_CACHED() to run injection points dir
12167 -->
12168
12169 <listitem>
12170 <para>
12171 Separate the loading and running of <link
12172 linkend="xfunc-addin-injection-points">injection points</link>
12173 (Michael Paquier, Heikki Linnakangas)
12174 <ulink url="&commit_baseurl;4b211003e">&sect;</ulink>
12175 <ulink url="&commit_baseurl;a0a5869a8">&sect;</ulink>
12176 </para>
12177
12178 <para>
12179 Injection points can now be created, but not run, via <link
12180 linkend="xfunc-addin-injection-points"><function>INJECTION_POINT_LOAD()</function></link>,
12181 and such injection points can be run via <link
12182 linkend="xfunc-addin-injection-points"><function>INJECTION_POINT_CACHED()</function></link>.
12183 </para>
12184 </listitem>
12185
12186 <!--
12187 Author: Michael Paquier <[email protected]>
12188 2025-05-10 [371f2db8b] Add support for runtime arguments in injection points
12189 -->
12190
12191 <listitem>
12192 <para>
12193 Support runtime arguments in injection points (Michael Paquier)
12194 <ulink url="&commit_baseurl;371f2db8b">&sect;</ulink>
12195 </para>
12196 </listitem>
12197
12198 <!--
12199 Author: Heikki Linnakangas <[email protected]>
12200 2024-07-26 [20e0e7da9] Add test for early backend startup errors
12201 -->
12202
12203 <listitem>
12204 <para>
12205 Allow inline injection point test code with <link
12206 linkend="xfunc-addin-injection-points"><function>IS_INJECTION_POINT_ATTACHED()</function></link>
12207 (Heikki Linnakangas)
12208 <ulink url="&commit_baseurl;20e0e7da9">&sect;</ulink>
12209 </para>
12210 </listitem>
12211
12212 <!--
12213 Author: David Rowley <[email protected]>
12214 2024-08-05 [ca6fde922] Optimize JSON escaping using SIMD
12215 -->
12216
12217 <listitem>
12218 <para>
12219 Improve the performance of processing long <link
12220 linkend="datatype-json"><type>JSON</type></link> strings using
12221 <acronym>SIMD</acronym> (Single Instruction Multiple Data) (David
12222 Rowley)
12223 <ulink url="&commit_baseurl;ca6fde922">&sect;</ulink>
12224 </para>
12225 </listitem>
12226
12227 <!--
12228 Author: John Naylor <[email protected]>
12229 2025-04-06 [3c6e8c123] Compute CRC32C using AVX-512 instructions where availabl
12230 -->
12231
12232 <listitem>
12233 <para>
12234 Speed up CRC32C calculations using x86 <acronym>AVX</acronym>-512
12235 instructions (Raghuveer Devulapalli, Paul Amonson)
12236 <ulink url="&commit_baseurl;3c6e8c123">&sect;</ulink>
12237 </para>
12238 </listitem>
12239
12240 <!--
12241 Author: Nathan Bossart <[email protected]>
12242 2025-03-28 [6be53c276] Optimize popcount functions with ARM Neon intrinsics.
12243 Author: Nathan Bossart <[email protected]>
12244 2025-03-28 [519338ace] Optimize popcount functions with ARM SVE intrinsics.
12245 -->
12246
12247 <listitem>
12248 <para>
12249 Add <acronym>ARM</acronym> Neon and <acronym>SVE CPU</acronym>
12250 intrinsics for popcount (integer bit counting) (Chiranmoy
12251 Bhattacharya, Devanga Susmitha, Rama Malladi)
12252 <ulink url="&commit_baseurl;6be53c276">&sect;</ulink>
12253 <ulink url="&commit_baseurl;519338ace">&sect;</ulink>
12254 </para>
12255 </listitem>
12256
12257 <!--
12258 Author: Dean Rasheed <[email protected]>
12259 2024-07-09 [ca481d3c9] Optimise numeric multiplication for short inputs.
12260 Author: Dean Rasheed <[email protected]>
12261 2024-08-15 [c4e44224c] Extend mul_var_short() to 5 and 6-digit inputs.
12262 Author: Dean Rasheed <[email protected]>
12263 2024-08-15 [8dc28d7eb] Optimise numeric multiplication using base-NBASE^2 arith
12264 Author: Dean Rasheed <[email protected]>
12265 2024-10-04 [9428c001f] Speed up numeric division by always using the "fast" alg
12266 -->
12267
12268 <listitem>
12269 <para>
12270 Improve the speed of numeric multiplication and division (Joel
12271 Jacobson, Dean Rasheed)
12272 <ulink url="&commit_baseurl;ca481d3c9">&sect;</ulink>
12273 <ulink url="&commit_baseurl;c4e44224c">&sect;</ulink>
12274 <ulink url="&commit_baseurl;8dc28d7eb">&sect;</ulink>
12275 <ulink url="&commit_baseurl;9428c001f">&sect;</ulink>
12276 </para>
12277 </listitem>
12278
12279 <!--
12280 Author: Tomas Vondra <[email protected]>
12281 2025-04-07 [65c298f61] Add support for basic NUMA awareness
12282 Author: Tomas Vondra <[email protected]>
12283 2025-04-07 [8cc139bec] Introduce pg_shmem_allocations_numa view
12284 Author: Tomas Vondra <[email protected]>
12285 2025-04-07 [ba2a3c230] Add pg_buffercache_numa view with NUMA node info
12286 -->
12287
12288 <listitem>
12289 <para>
12290 Add configure option <link
12291 linkend="configure-option-with-libnuma"><option>--with-libnuma</option></link>
12292 to enable <acronym>NUMA</acronym> awareness (Jakub Wartak, Bertrand
12293 Drouvot)
12294 <ulink url="&commit_baseurl;65c298f61">&sect;</ulink>
12295 <ulink url="&commit_baseurl;8cc139bec">&sect;</ulink>
12296 <ulink url="&commit_baseurl;ba2a3c230">&sect;</ulink>
12297 </para>
12298
12299 <para>
12300 The function <link
12301 linkend="functions-info-session-table"><function>pg_numa_available()</function></link>
12302 reports on <acronym>NUMA</acronym> awareness, and system views <link
12303 linkend="view-pg-shmem-allocations-numa"><structname>pg_shmem_allocations_numa</structname></link>
12304 and <link
12305 linkend="pgbuffercache-pg-buffercache-numa"><structname>pg_buffercache_numa</structname></link>
12306 which report on shared memory distribution across
12307 <acronym>NUMA</acronym> nodes.
12308 </para>
12309 </listitem>
12310
12311 <!--
12312 Author: Nathan Bossart <[email protected]>
12313 2024-09-18 [b52c4fc3c] Add TOAST table to pg_index.
12314 -->
12315
12316 <listitem>
12317 <para>
12318 Add <link
12319 linkend="storage-toast"><acronym>TOAST</acronym></link> table to <link
12320 linkend="catalog-pg-index"><structname>pg_index</structname></link>
12321 to allow for very large expression indexes (Nathan Bossart)
12322 <ulink url="&commit_baseurl;b52c4fc3c">&sect;</ulink>
12323 </para>
12324 </listitem>
12325
12326 <!--
12327 Author: David Rowley <[email protected]>
12328 2024-12-20 [02a8d0c45] Remove pg_attribute.attcacheoff column
12329 -->
12330
12331 <listitem>
12332 <para>
12333 Remove column <link
12334 linkend="catalog-pg-attribute"><structname>pg_attribute</structname></link>.<structfield>attcacheoff</structfield>
12335 (David Rowley)
12336 <ulink url="&commit_baseurl;02a8d0c45">&sect;</ulink>
12337 </para>
12338 </listitem>
12339
12340 <!--
12341 Author: Melanie Plageman <[email protected]>
12342 2025-03-03 [99f8f3fbb] Add relallfrozen to pg_class
12343 -->
12344
12345 <listitem>
12346 <para>
12347 Add column <link
12348 linkend="catalog-pg-class"><structname>pg_class</structname></link>.<structfield>relallfrozen</structfield>
12349 (Melanie Plageman)
12350 <ulink url="&commit_baseurl;99f8f3fbb">&sect;</ulink>
12351 </para>
12352 </listitem>
12353
12354 <!--
12355 Author: Peter Eisentraut <[email protected]>
12356 2024-09-10 [56fead44d] Add amgettreeheight index AM API routine
12357 Author: Peter Eisentraut <[email protected]>
12358 2025-03-07 [af4002b38] Rename amcancrosscompare
12359 -->
12360
12361 <listitem>
12362 <para>
12363 Add <link
12364 linkend="indexam"><structfield>amgettreeheight</structfield></link>,
12365 <literal>amconsistentequality</literal>, and
12366 <literal>amconsistentordering</literal> to the index access method
12367 <acronym>API</acronym> (Mark Dilger)
12368 <ulink url="&commit_baseurl;56fead44d">&sect;</ulink>
12369 <ulink url="&commit_baseurl;af4002b38">&sect;</ulink>
12370 </para>
12371 </listitem>
12372
12373 <!--
12374 Author: Peter Eisentraut <[email protected]>
12375 2024-09-17 [7406ab623] Add stratnum GiST support function
12376 -->
12377
12378 <listitem>
12379 <para>
12380 Add GiST support function <link
12381 linkend="gist-extensibility"><function>stratnum()</function></link>
12382 (Paul A. Jungwirth)
12383 <ulink url="&commit_baseurl;7406ab623">&sect;</ulink>
12384 </para>
12385 </listitem>
12386
12387 <!--
12388 Author: Masahiko Sawada <[email protected]>
12389 2025-02-21 [44fe30fda] Add default_char_signedness field to ControlFileData.
12390 -->
12391
12392 <listitem>
12393 <para>
12394 Record the default <acronym>CPU</acronym> signedness of
12395 <literal>char</literal> in <xref linkend="app-pgcontroldata"/>
12396 (Masahiko Sawada)
12397 <ulink url="&commit_baseurl;44fe30fda">&sect;</ulink>
12398 </para>
12399 </listitem>
12400
12401 <!--
12402 Author: Peter Eisentraut <[email protected]>
12403 2025-03-12 [72a3d0462] Prepare for Python "Limited API" in PL/Python
12404 Author: Peter Eisentraut <[email protected]>
12405 2025-03-14 [0793ab810] Activate Python "Limited API" in PL/Python
12406 -->
12407
12408 <listitem>
12409 <para>
12410 Add support for Python "Limited <acronym>API</acronym>" in <link
12411 linkend="plpython">PL/Python</link> (Peter Eisentraut)
12412 <ulink url="&commit_baseurl;72a3d0462">&sect;</ulink>
12413 <ulink url="&commit_baseurl;0793ab810">&sect;</ulink>
12414 </para>
12415
12416 <para>
12417 This helps prevent problems caused by
12418 <application>Python</application> 3.x version mismatches.
12419 </para>
12420 </listitem>
12421
12422 <!--
12423 Author: Jacob Champion <[email protected]>
12424 2025-04-29 [45363fca6] Bump the minimum supported Python version to 3.6.8
12425 -->
12426
12427 <listitem>
12428 <para>
12429 Change the minimum supported <application>Python</application>
12430 version to 3.6.8 (Jacob Champion)
12431 <ulink url="&commit_baseurl;45363fca6">&sect;</ulink>
12432 </para>
12433 </listitem>
12434
12435 <!--
12436 Author: Daniel Gustafsson <[email protected]>
12437 2024-09-02 [a70e01d43] Remove support for OpenSSL older than 1.1.0
12438 Author: Daniel Gustafsson <[email protected]>
12439 2024-10-24 [6c66b7443] Raise the minimum supported OpenSSL version to 1.1.1
12440 -->
12441
12442 <listitem>
12443 <para>
12444 Remove support for <application>OpenSSL</application> versions older
12445 than 1.1.1 (Daniel Gustafsson)
12446 <ulink url="&commit_baseurl;a70e01d43">&sect;</ulink>
12447 <ulink url="&commit_baseurl;6c66b7443">&sect;</ulink>
12448 </para>
12449 </listitem>
12450
12451 <!--
12452 Author: Peter Eisentraut <[email protected]>
12453 2024-10-01 [972c2cd28] jit: Require at least LLVM 14, if enabled.
12454 -->
12455
12456 <listitem>
12457 <para>
12458 If <application>LLVM</application> is enabled, require version 14
12459 or later (Thomas Munro)
12460 <ulink url="&commit_baseurl;972c2cd28">&sect;</ulink>
12461 </para>
12462 </listitem>
12463
12464 <!--
12465 Author: Tom Lane <[email protected]>
12466 2025-03-26 [9324c8c58] Introduce PG_MODULE_MAGIC_EXT macro.
12467 -->
12468
12469 <listitem>
12470 <para>
12471 Add macro <link
12472 linkend="functions-info"><literal>PG_MODULE_MAGIC_EXT</literal></link>
12473 to allow extensions to report their name and version (Andrei Lepikhov)
12474 <ulink url="&commit_baseurl;9324c8c58">&sect;</ulink>
12475 </para>
12476
12477 <para>
12478 This information can be access via the new function <link
12479 linkend="functions-info-session-table"><function>pg_get_loaded_modules()</function></link>.
12480 </para>
12481 </listitem>
12482
12483 <!--
12484 Author: Tom Lane <[email protected]>
12485 2024-09-09 [218527d01] Don't bother checking the result of SPI_connect[_ext] an
12486 -->
12487
12488 <listitem>
12489 <para>
12490 Document that <link
12491 linkend="spi-spi-connect"><function>SPI_connect()</function></link>/<link
12492 linkend="spi-spi-connect"><function>SPI_connect_ext()</function></link>
12493 always returns success (<literal>SPI_OK_CONNECT</literal>) (Stepan
12494 Neretin)
12495 <ulink url="&commit_baseurl;218527d01">&sect;</ulink>
12496 </para>
12497
12498 <para>
12499 Errors are always reported via <function>ereport()</function>.
12500 </para>
12501 </listitem>
12502
12503 <!--
12504 Author: Peter Eisentraut <[email protected]>
12505 2024-07-31 [e54a42ac9] Add API and ABI stability guidance to the C language doc
12506 -->
12507
12508 <listitem>
12509 <para>
12510 Add <link linkend="xfunc-api-abi-stability-guidance">documentation
12511 section</link> about <acronym>API</acronym> and <acronym>ABI</acronym>
12512 compatibility (David Wheeler, Peter Eisentraut)
12513 <ulink url="&commit_baseurl;e54a42ac9">&sect;</ulink>
12514 </para>
12515 </listitem>
12516
12517 <!--
12518 Author: Peter Eisentraut <[email protected]>
12519 2025-01-27 [5afaba629] doc: Meson is not experimental on Windows
12520 -->
12521
12522 <listitem>
12523 <para>
12524 Remove the experimental designation of
12525 <application>Meson</application> builds on <systemitem
12526 class="osname">Windows</systemitem> (Aleksander Alekseev)
12527 <ulink url="&commit_baseurl;5afaba629">&sect;</ulink>
12528 </para>
12529 </listitem>
12530
12531 <!--
12532 Author: Thomas Munro <[email protected]>
12533 2024-07-30 [e25626677] Remove - -disable-spinlocks.
12534 Author: Thomas Munro <[email protected]>
12535 2024-07-30 [813852613] Remove - -disable-atomics, require 32 bit atomics.
12536 -->
12537
12538 <listitem>
12539 <para>
12540 Remove configure options <option>--disable-spinlocks</option> and
12541 <option>--disable-atomics</option> (Thomas Munro)
12542 <ulink url="&commit_baseurl;e25626677">&sect;</ulink>
12543 <ulink url="&commit_baseurl;813852613">&sect;</ulink>
12544 </para>
12545
12546 <para>
12547 Thirty-two-bit atomic operations are now required.
12548 </para>
12549 </listitem>
12550
12551 <!--
12552 Author: Tom Lane <[email protected]>
12553 2024-07-01 [edadeb071] Remove support for HPPA (a/k/a PA-RISC) architecture.
12554 -->
12555
12556 <listitem>
12557 <para>
12558 Remove support for the
12559 <acronym>HPPA</acronym>/<acronym>PA-RISC</acronym> architecture
12560 (Tom Lane)
12561 <ulink url="&commit_baseurl;edadeb071">&sect;</ulink>
12562 </para>
12563 </listitem>
12564
12565 </itemizedlist>
12566
12567 </sect3>
12568
12569 <sect3 id="release-18-modules">
12570 <title>Additional Modules</title>
12571
12572 <itemizedlist>
12573
12574 <!--
12575 Author: Masahiko Sawada <[email protected]>
12576 2024-10-14 [7cdfeee32] Add contrib/pg_logicalinspect.
12577 -->
12578
12579 <listitem>
12580 <para>
12581 Add extension <xref linkend="pglogicalinspect"/> to inspect logical
12582 snapshots (Bertrand Drouvot)
12583 <ulink url="&commit_baseurl;7cdfeee32">&sect;</ulink>
12584 </para>
12585 </listitem>
12586
12587 <!--
12588 Author: Robert Haas <[email protected]>
12589 2025-03-26 [8d5ceb113] pg_overexplain: Additional EXPLAIN options for debugging
12590 -->
12591
12592 <listitem>
12593 <para>
12594 Add extension <xref linkend="pgoverexplain"/> which adds debug details
12595 to <link linkend="sql-explain"><command>EXPLAIN</command></link>
12596 output (Robert Haas)
12597 <ulink url="&commit_baseurl;8d5ceb113">&sect;</ulink>
12598 </para>
12599 </listitem>
12600
12601 <!--
12602 Author: Fujii Masao <[email protected]>
12603 2024-07-26 [c297a47c5] postgres_fdw: Add "used_in_xact" column to postgres_fdw_
12604 Author: Fujii Masao <[email protected]>
12605 2024-07-26 [857df3cef] postgres_fdw: Add connection status check to postgres_fd
12606 Author: Fujii Masao <[email protected]>
12607 2024-09-18 [4f08ab554] postgres_fdw: Extend postgres_fdw_get_connections to ret
12608 Author: Fujii Masao <[email protected]>
12609 2025-03-03 [fe186bda7] postgres_fdw: Extend postgres_fdw_get_connections to ret
12610 -->
12611
12612 <listitem>
12613 <para>
12614 Add output columns to <link
12615 linkend="postgres-fdw-functions"><function>postgres_fdw_get_connections()</function></link>
12616 (Hayato Kuroda, Sagar Dilip Shedge)
12617 <ulink url="&commit_baseurl;c297a47c5">&sect;</ulink>
12618 <ulink url="&commit_baseurl;857df3cef">&sect;</ulink>
12619 <ulink url="&commit_baseurl;4f08ab554">&sect;</ulink>
12620 <ulink url="&commit_baseurl;fe186bda7">&sect;</ulink>
12621 </para>
12622
12623 <para>
12624 New output column <structfield>used_in_xact</structfield> indicates
12625 if the foreign data wrapper is being used by a current transaction,
12626 <structfield>closed</structfield> indicates if it is closed,
12627 <structfield>user_name</structfield> indicates the user name, and
12628 <structfield>remote_backend_pid</structfield> indicates the remote
12629 backend process identifier.
12630 </para>
12631 </listitem>
12632
12633 <!--
12634 Author: Peter Eisentraut <[email protected]>
12635 2025-01-15 [761c79508] postgres_fdw: SCRAM authentication pass-through
12636 -->
12637
12638 <listitem>
12639 <para>
12640 Allow <link linkend="auth-password"><acronym>SCRAM</acronym></link>
12641 authentication from the client to be passed to <xref
12642 linkend="postgres-fdw"/> servers (Matheus Alcantara, Peter Eisentraut)
12643 <ulink url="&commit_baseurl;761c79508">&sect;</ulink>
12644 </para>
12645
12646 <para>
12647 This avoids storing <application>postgres_fdw</application>
12648 authentication information in the database, and is
12649 enabled with the <application>postgres_fdw</application> <link
12650 linkend="postgres-fdw-option-use-scram-passthrough"><literal>use_scram_passthrough</literal></link>
12651 connection option. libpq uses new connection parameters
12652 <xref linkend="libpq-connect-scram-client-key"/> and <xref
12653 linkend="libpq-connect-scram-server-key"/>.
12654 </para>
12655 </listitem>
12656
12657 <!--
12658 Author: Peter Eisentraut <[email protected]>
12659 2025-03-26 [3642df265] dblink: SCRAM authentication pass-through
12660 -->
12661
12662 <listitem>
12663 <para>
12664 Allow <acronym>SCRAM</acronym> authentication from the client to be
12665 passed to <xref linkend="dblink"/> servers (Matheus Alcantara)
12666 <ulink url="&commit_baseurl;3642df265">&sect;</ulink>
12667 </para>
12668 </listitem>
12669
12670 <!--
12671 Author: Fujii Masao <[email protected]>
12672 2024-10-03 [a1c4c8a9e] file_fdw: Add on_error and log_verbosity options to file
12673 -->
12674
12675 <listitem>
12676 <para>
12677 Add <literal>on_error</literal> and <literal>log_verbosity</literal>
12678 options to <xref linkend="file-fdw"/> (Atsushi Torikoshi)
12679 <ulink url="&commit_baseurl;a1c4c8a9e">&sect;</ulink>
12680 </para>
12681
12682 <para>
12683 These control how <application>file_fdw</application> handles and
12684 reports invalid file rows.
12685 </para>
12686 </listitem>
12687
12688 <!--
12689 Author: Fujii Masao <[email protected]>
12690 2024-11-20 [6c8f67032] file_fdw: Add REJECT_LIMIT option to file_fdw.
12691 -->
12692
12693 <listitem>
12694 <para>
12695 Add <literal>reject_limit</literal> to control the number of
12696 invalid rows <application>file_fdw</application> can ignore (Atsushi
12697 Torikoshi)
12698 <ulink url="&commit_baseurl;6c8f67032">&sect;</ulink>
12699 </para>
12700
12701 <para>
12702 This is active when <literal>ON_ERROR = 'ignore'</literal>.
12703 </para>
12704 </listitem>
12705
12706 <!--
12707 Author: Nathan Bossart <[email protected]>
12708 2025-01-07 [f7e1b3828] Add passwordcheck.min_password_length.
12709 -->
12710
12711 <listitem>
12712 <para>
12713 Add configurable variable <varname>min_password_length</varname> to
12714 <xref linkend="passwordcheck"/> (Emanuele Musella, Maurizio Boriani)
12715 <ulink url="&commit_baseurl;f7e1b3828">&sect;</ulink>
12716 </para>
12717
12718 <para>
12719 This controls the minimum password length.
12720 </para>
12721 </listitem>
12722
12723 <!--
12724 Author: Tatsuo Ishii <[email protected]>
12725 2024-10-11 [cae0f3c40] pgbench: Improve result outputs related to failed transa
12726 -->
12727
12728 <listitem>
12729 <para>
12730 Have <xref linkend="pgbench"/> report the number of failed, retried,
12731 or skipped transactions in per-script reports (Yugo Nagata)
12732 <ulink url="&commit_baseurl;cae0f3c40">&sect;</ulink>
12733 </para>
12734 </listitem>
12735
12736 <!--
12737 Author: Tom Lane <[email protected]>
12738 2025-03-16 [448904423] contrib/isn: Make weak mode a GUC setting, and fix relat
12739 -->
12740
12741 <listitem>
12742 <para>
12743 Add <xref linkend="isn"/> server variable <literal>weak</literal>
12744 to control invalid check digit acceptance (Viktor Holmberg)
12745 <ulink url="&commit_baseurl;448904423">&sect;</ulink>
12746 </para>
12747
12748 <para>
12749 This was previously only controlled by function <link
12750 linkend="isn-functions"><function>isn_weak()</function></link>.
12751 </para>
12752 </listitem>
12753
12754 <!--
12755 Author: Heikki Linnakangas <[email protected]>
12756 2025-04-03 [e4309f73f] Add support for sorted gist index builds to btree_gist
12757 -->
12758
12759 <listitem>
12760 <para>
12761 Allow values to be sorted to speed <xref linkend="btree-gist"/>
12762 index builds (Bernd Helmle, Andrey Borodin)
12763 <ulink url="&commit_baseurl;e4309f73f">&sect;</ulink>
12764 </para>
12765 </listitem>
12766
12767 <!--
12768 Author: Tomas Vondra <[email protected]>
12769 2025-03-29 [14ffaece0] amcheck: Add gin_index_check() to verify GIN index
12770 -->
12771
12772 <listitem>
12773 <para>
12774 Add <xref linkend="amcheck"/> check function <link
12775 linkend="amcheck-functions"><function>gin_index_check()</function></link>
12776 to verify <literal>GIN</literal> indexes (Grigory Kryachko, Heikki
12777 Linnakangas, Andrey Borodin)
12778 <ulink url="&commit_baseurl;14ffaece0">&sect;</ulink>
12779 </para>
12780 </listitem>
12781
12782 <!--
12783 Author: Andres Freund <[email protected]>
12784 2025-04-08 [dcf7e1697] Add pg_buffercache_evict_{relation,all} functions
12785 -->
12786
12787 <listitem>
12788 <para>
12789 Add functions <link
12790 linkend="pgbuffercache-pg-buffercache-evict-relation"><function>pg_buffercache_evict_relation()</function></link>
12791 and <link
12792 linkend="pgbuffercache-pg-buffercache-evict-all"><function>pg_buffercache_evict_all()</function></link>
12793 to evict unpinned shared buffers (Nazir Bilal Yavuz)
12794 <ulink url="&commit_baseurl;dcf7e1697">&sect;</ulink>
12795 </para>
12796
12797 <para>
12798 The existing function <link
12799 linkend="pgbuffercache-pg-buffercache-evict"><function>pg_buffercache_evict()</function></link>
12800 now returns the buffer flush status.
12801 </para>
12802 </listitem>
12803
12804 <!--
12805 Author: Robert Haas <[email protected]>
12806 2025-03-18 [c65bc2e1d] Make it possible for loadable modules to add EXPLAIN opt
12807 Author: Robert Haas <[email protected]>
12808 2025-03-18 [4fd02bf7c] Add some new hooks so extensions can add details to EXPL
12809 Author: Robert Haas <[email protected]>
12810 2025-03-20 [50ba65e73] Add an additional hook for EXPLAIN option validation.
12811 -->
12812
12813 <listitem>
12814 <para>
12815 Allow extensions to install custom <xref linkend="sql-explain"/>
12816 options (Robert Haas, Sami Imseih)
12817 <ulink url="&commit_baseurl;c65bc2e1d">&sect;</ulink>
12818 <ulink url="&commit_baseurl;4fd02bf7c">&sect;</ulink>
12819 <ulink url="&commit_baseurl;50ba65e73">&sect;</ulink>
12820 </para>
12821 </listitem>
12822
12823 <!--
12824 Author: Michael Paquier <[email protected]>
12825 2024-08-04 [7949d9594] Introduce pluggable APIs for Cumulative Statistics
12826 Author: Michael Paquier <[email protected]>
12827 2024-08-05 [2eff9e678] Add helper routines to retrieve data for custom fixed-nu
12828 -->
12829
12830 <listitem>
12831 <para>
12832 Allow extensions to use the server's cumulative statistics
12833 <acronym>API</acronym> (Michael Paquier)
12834 <ulink url="&commit_baseurl;7949d9594">&sect;</ulink>
12835 <ulink url="&commit_baseurl;2eff9e678">&sect;</ulink>
12836 </para>
12837 </listitem>
12838
12839 </itemizedlist>
12840
12841 <sect4 id="release-18-pgstatstatements">
12842 <title><xref linkend="pgstatstatements"/></title>
12843
12844 <itemizedlist>
12845
12846 <!--
12847 Author: Michael Paquier <[email protected]>
12848 2024-10-28 [6b652e6ce] Set query ID for inner queries of CREATE TABLE AS and DE
12849 -->
12850
12851 <listitem>
12852 <para>
12853 Allow the queries of <xref linkend="sql-createtableas"/>
12854 and <xref linkend="sql-declare"/> to be tracked by
12855 <application>pg_stat_statements</application> (Anthonin Bonnefoy)
12856 <ulink url="&commit_baseurl;6b652e6ce">&sect;</ulink>
12857 </para>
12858
12859 <para>
12860 They are also now assigned query ids.
12861 </para>
12862 </listitem>
12863
12864 <!--
12865 Author: Michael Paquier <[email protected]>
12866 2024-09-30 [dc6851596] Show values of SET statements as constants in pg_stat_st
12867 -->
12868
12869 <listitem>
12870 <para>
12871 Allow the parameterization of <xref linkend="sql-set"/> values in
12872 <application>pg_stat_statements</application> (Greg Sabino Mullane,
12873 Michael Paquier)
12874 <ulink url="&commit_baseurl;dc6851596">&sect;</ulink>
12875 </para>
12876
12877 <para>
12878 This reduces the bloat caused by <command>SET</command> statements
12879 with differing constants.
12880 </para>
12881 </listitem>
12882
12883 <!--
12884 Author: Michael Paquier <[email protected]>
12885 2024-10-09 [cf54a2c00] pg_stat_statements: Add columns to track parallel worker
12886 -->
12887
12888 <listitem>
12889 <para>
12890 Add <link
12891 linkend="pgstatstatements-pg-stat-statements"><structname>pg_stat_statements</structname></link>
12892 columns to report parallel activity (Guillaume Lelarge)
12893 <ulink url="&commit_baseurl;cf54a2c00">&sect;</ulink>
12894 </para>
12895
12896 <para>
12897 The new columns are
12898 <structfield>parallel_workers_to_launch</structfield> and
12899 <structfield>parallel_workers_launched</structfield>.
12900 </para>
12901 </listitem>
12902
12903 <!--
12904 Author: Michael Paquier <[email protected]>
12905 2025-02-17 [ce5bcc4a9] pg_stat_statements: Add wal_buffers_full
12906 -->
12907
12908 <listitem>
12909 <para>
12910 Add
12911 <structname>pg_stat_statements</structname>.<structfield>wal_buffers_full</structfield>
12912 to report full <acronym>WAL</acronym> buffers (Bertrand Drouvot)
12913 <ulink url="&commit_baseurl;ce5bcc4a9">&sect;</ulink>
12914 </para>
12915 </listitem>
12916
12917 </itemizedlist>
12918
12919 </sect4>
12920
12921 <sect4 id="release-18-pgcrypto">
12922 <title><xref linkend="pgcrypto"/></title>
12923
12924 <itemizedlist>
12925
12926 <!--
12927 Author: Álvaro Herrera <[email protected]>
12928 2025-04-05 [749a9e20c] Add modern SHA-2 based password hashes to pgcrypto.
12929 -->
12930
12931 <listitem>
12932 <para>
12933 Add <application>pgcrypto</application> algorithms <link
12934 linkend="pgcrypto-crypt-algorithms"><literal>sha256crypt</literal></link>
12935 and <link
12936 linkend="pgcrypto-crypt-algorithms"><literal>sha512crypt</literal></link>
12937 (Bernd Helmle)
12938 <ulink url="&commit_baseurl;749a9e20c">&sect;</ulink>
12939 </para>
12940 </listitem>
12941
12942 <!--
12943 Author: Daniel Gustafsson <[email protected]>
12944 2025-02-14 [9ad1b3d01] pgcrypto: Add support for CFB mode in AES encryption
12945 -->
12946
12947 <listitem>
12948 <para>
12949 Add <link
12950 linkend="pgcrypto-raw-enc-funcs"><acronym>CFB</acronym></link> mode
12951 to <application>pgcrypto</application> encryption and decryption
12952 (Umar Hayat)
12953 <ulink url="&commit_baseurl;9ad1b3d01">&sect;</ulink>
12954 </para>
12955 </listitem>
12956
12957 <!--
12958 Author: Daniel Gustafsson <[email protected]>
12959 2025-01-24 [924d89a35] pgcrypto: Add function to check FIPS mode
12960 -->
12961
12962 <listitem>
12963 <para>
12964 Add function <link
12965 linkend="pgcrypto-openssl-support-funcs"><function>fips_mode()</function></link>
12966 to report the server's <acronym>FIPS</acronym> mode (Daniel
12967 Gustafsson)
12968 <ulink url="&commit_baseurl;924d89a35">&sect;</ulink>
12969 </para>
12970 </listitem>
12971
12972 <!--
12973 Author: Daniel Gustafsson <[email protected]>
12974 2025-01-24 [035f99cbe] pgcrypto: Make it possible to disable built-in crypto
12975 -->
12976
12977 <listitem>
12978 <para>
12979 Add <application>pgcrypto</application> server variable <link
12980 linkend="pgcrypto-configuration-parameters-builtin_crypto_enabled"><varname>builtin_crypto_enabled</varname></link>
12981 to allow disabling builtin non-<acronym>FIPS</acronym> mode
12982 cryptographic functions (Daniel Gustafsson, Joe Conway)
12983 <ulink url="&commit_baseurl;035f99cbe">&sect;</ulink>
12984 </para>
12985
12986 <para>
12987 This is useful for guaranteeing <acronym>FIPS</acronym> mode behavior.
12988 </para>
12989 </listitem>
12990
12991 </itemizedlist>
12992 </sect4>
12993
12994 </sect3>
12995
12996 </sect2>
12997
12998 <sect2 id="release-18-acknowledgements">
12999 <title>Acknowledgments</title>
13000
13001 <para>
13002 The following individuals (in alphabetical order) have contributed
13003 to this release as patch authors, committers, reviewers, testers,
13004 or reporters of issues.
13005 </para>
13006
13007 <simplelist>
13008 <member>Abhishek Chanda</member>
13009 <member>Adam Guo</member>
13010 <member>Adam Rauch</member>
13011 <member>Aidar Imamov</member>
13012 <member>Ajin Cherian</member>
13013 <member>Alastair Turner</member>
13014 <member>Alec Cozens</member>
13015 <member>Aleksander Alekseev</member>
13016 <member>Alena Rybakina</member>
13017 <member>Alex Friedman</member>
13018 <member>Alex Richman</member>
13019 <member>Alexander Alehin</member>
13020 <member>Alexander Borisov</member>
13021 <member>Alexander Korotkov</member>
13022 <member>Alexander Kozhemyakin</member>
13023 <member>Alexander Kukushkin</member>
13024 <member>Alexander Kuzmenkov</member>
13025 <member>Alexander Kuznetsov</member>
13026 <member>Alexander Lakhin</member>
13027 <member>Alexander Pyhalov</member>
13028 <member>Alexandra Wang</member>
13029 <member>Alexey Dvoichenkov</member>
13030 <member>Alexey Makhmutov</member>
13031 <member>Alexey Shishkin</member>
13032 <member>Ali Akbar</member>
13033 <member>Álvaro Herrera</member>
13034 <member>Álvaro Mongil</member>
13035 <member>Amit Kapila</member>
13036 <member>Amit Langote</member>
13037 <member>Amul Sul</member>
13038 <member>Andreas Karlsson</member>
13039 <member>Andreas Scherbaum</member>
13040 <member>Andreas Ulbrich</member>
13041 <member>Andrei Lepikhov</member>
13042 <member>Andres Freund</member>
13043 <member>Andrew</member>
13044 <member>Andrew Bille</member>
13045 <member>Andrew Dunstan</member>
13046 <member>Andrew Jackson</member>
13047 <member>Andrew Kane</member>
13048 <member>Andrew Watkins</member>
13049 <member>Andrey Borodin</member>
13050 <member>Andrey Chudnovsky</member>
13051 <member>Andrey Rachitskiy</member>
13052 <member>Andrey Rudometov</member>
13053 <member>Andy Alsup</member>
13054 <member>Andy Fan</member>
13055 <member>Anthonin Bonnefoy</member>
13056 <member>Anthony Hsu</member>
13057 <member>Anthony Leung</member>
13058 <member>Anton Melnikov</member>
13059 <member>Anton Voloshin</member>
13060 <member>Antonin Houska</member>
13061 <member>Antti Lampinen</member>
13062 <member>Arseniy Mukhin</member>
13063 <member>Artur Zakirov</member>
13064 <member>Arun Thirupathi</member>
13065 <member>Ashutosh Bapat</member>
13066 <member>Asphator</member>
13067 <member>Atsushi Torikoshi</member>
13068 <member>Avi Weinberg</member>
13069 <member>Aya Iwata</member>
13070 <member>Ayush Tiwari</member>
13071 <member>Ayush Vatsa</member>
13072 <member>Bastien Roucariès</member>
13073 <member>Ben Peachey Higdon</member>
13074 <member>Benoit Lobréau</member>
13075 <member>Bernd Helmle</member>
13076 <member>Bernd Reiß</member>
13077 <member>Bernhard Wiedemann</member>
13078 <member>Bertrand Drouvot</member>
13079 <member>Bertrand Mamasam</member>
13080 <member>Bharath Rupireddy</member>
13081 <member>Bogdan Grigorenko</member>
13082 <member>Boyu Yang</member>
13083 <member>Braulio Fdo Gonzalez</member>
13084 <member>Bruce Momjian</member>
13085 <member>Bykov Ivan</member>
13086 <member>Cameron Vogt</member>
13087 <member>Cary Huang</member>
13088 <member>Cédric Villemain</member>
13089 <member>Cees van Zeeland</member>
13090 <member>ChangAo Chen</member>
13091 <member>Chao Li</member>
13092 <member>Chapman Flack</member>
13093 <member>Charles Samborski</member>
13094 <member>Chengwen Wu</member>
13095 <member>Chengxi Sun</member>
13096 <member>Chiranmoy Bhattacharya</member>
13097 <member>Chris Gooch</member>
13098 <member>Christian Charukiewicz</member>
13099 <member>Christoph Berg</member>
13100 <member>Christophe Courtois</member>
13101 <member>Christopher Inokuchi</member>
13102 <member>Clemens Ruck</member>
13103 <member>Corey Huinker</member>
13104 <member>Craig Milhiser</member>
13105 <member>Crisp Lee</member>
13106 <member>Dagfinn Ilmari Mannsåker</member>
13107 <member>Daniel Elishakov</member>
13108 <member>Daniel Gustafsson</member>
13109 <member>Daniel Vérité</member>
13110 <member>Daniel Westermann</member>
13111 <member>Daniele Varrazzo</member>
13112 <member>Daniil Davydov</member>
13113 <member>Daria Shanina</member>
13114 <member>Dave Cramer</member>
13115 <member>Dave Page</member>
13116 <member>David Benjamin</member>
13117 <member>David Christensen</member>
13118 <member>David Fiedler</member>
13119 <member>David G. Johnston</member>
13120 <member>David Geier</member>
13121 <member>David Rowley</member>
13122 <member>David Steele</member>
13123 <member>David Wheeler</member>
13124 <member>David Zhang</member>
13125 <member>Davinder Singh</member>
13126 <member>Dean Rasheed</member>
13127 <member>Devanga Susmitha</member>
13128 <member>Devrim Gündüz</member>
13129 <member>Dian Fay</member>
13130 <member>Dilip Kumar</member>
13131 <member>Dimitrios Apostolou</member>
13132 <member>Dipesh Dhameliya</member>
13133 <member>Dmitrii Bondar</member>
13134 <member>Dmitry Dolgov</member>
13135 <member>Dmitry Koval</member>
13136 <member>Dmitry Kovalenko</member>
13137 <member>Dmitry Yurichev</member>
13138 <member>Dominique Devienne</member>
13139 <member>Donghang Lin</member>
13140 <member>Dorjpalam Batbaatar</member>
13141 <member>Drew Callahan</member>
13142 <member>Duncan Sands</member>
13143 <member>Dwayne Towell</member>
13144 <member>Dzmitry Jachnik</member>
13145 <member>Egor Chindyaskin</member>
13146 <member>Egor Rogov</member>
13147 <member>Emanuel Ionescu</member>
13148 <member>Emanuele Musella</member>
13149 <member>Emre Hasegeli</member>
13150 <member>Eric Cyr</member>
13151 <member>Erica Zhang</member>
13152 <member>Erik Nordström</member>
13153 <member>Erik Rijkers</member>
13154 <member>Erik Wienhold</member>
13155 <member>Erki Eessaar</member>
13156 <member>Ethan Mertz</member>
13157 <member>Etienne LAFARGE</member>
13158 <member>Etsuro Fujita</member>
13159 <member>Euler Taveira</member>
13160 <member>Evan Si</member>
13161 <member>Evgeniy Gorbanev</member>
13162 <member>Fabio R. Sluzala</member>
13163 <member>Fabrízio de Royes Mello</member>
13164 <member>Feike Steenbergen</member>
13165 <member>Feliphe Pozzer</member>
13166 <member>Felix</member>
13167 <member>Fire Emerald</member>
13168 <member>Florents Tselai</member>
13169 <member>Francesco Degrassi</member>
13170 <member>Frank Streitzig</member>
13171 <member>Frédéric Yhuel</member>
13172 <member>Fredrik Widlert</member>
13173 <member>Gabriele Bartolini</member>
13174 <member>Gavin Panella</member>
13175 <member>Geoff Winkless</member>
13176 <member>George MacKerron</member>
13177 <member>Gilles Darold</member>
13178 <member>Grant Gryczan</member>
13179 <member>Greg Burd</member>
13180 <member>Greg Sabino Mullane</member>
13181 <member>Greg Stark</member>
13182 <member>Grigory Kryachko</member>
13183 <member>Guillaume Lelarge</member>
13184 <member>Gunnar Morling</member>
13185 <member>Gunnar Wagner</member>
13186 <member>Gurjeet Singh</member>
13187 <member>Haifang Wang</member>
13188 <member>Hajime Matsunaga</member>
13189 <member>Hamid Akhtar</member>
13190 <member>Hannu Krosing</member>
13191 <member>Hari Krishna Sunder</member>
13192 <member>Haruka Takatsuka</member>
13193 <member>Hayato Kuroda</member>
13194 <member>Heikki Linnakangas</member>
13195 <member>Hironobu Suzuki</member>
13196 <member>Holger Jakobs</member>
13197 <member>Hubert Lubaczewski</member>
13198 <member>Hugo Dubois</member>
13199 <member>Hugo Zhang</member>
13200 <member>Hunaid Sohail</member>
13201 <member>Hywel Carver</member>
13202 <member>Ian Barwick</member>
13203 <member>Ibrar Ahmed</member>
13204 <member>Igor Gnatyuk</member>
13205 <member>Igor Korot</member>
13206 <member>Ilia Evdokimov</member>
13207 <member>Ilya Gladyshev</member>
13208 <member>Ilyasov Ian</member>
13209 <member>Imran Zaheer</member>
13210 <member>Isaac Morland</member>
13211 <member>Israel Barth Rubio</member>
13212 <member>Ivan Kush</member>
13213 <member>Jacob Brazeal</member>
13214 <member>Jacob Champion</member>
13215 <member>Jaime Casanova</member>
13216 <member>Jakob Egger</member>
13217 <member>Jakub Wartak</member>
13218 <member>James Coleman</member>
13219 <member>James Hunter</member>
13220 <member>Jan Behrens</member>
13221 <member>Japin Li</member>
13222 <member>Jason Smith</member>
13223 <member>Jayesh Dehankar</member>
13224 <member>Jeevan Chalke</member>
13225 <member>Jeff Davis</member>
13226 <member>Jehan-Guillaume de Rorthais</member>
13227 <member>Jelte Fennema-Nio</member>
13228 <member>Jian He</member>
13229 <member>Jianghua Yang</member>
13230 <member>Jiao Shuntian</member>
13231 <member>Jim Jones</member>
13232 <member>Jim Nasby</member>
13233 <member>Jingtang Zhang</member>
13234 <member>Jingzhou Fu</member>
13235 <member>Joe Conway</member>
13236 <member>Joel Jacobson</member>
13237 <member>John Hutchins</member>
13238 <member>John Naylor</member>
13239 <member>Jonathan Katz</member>
13240 <member>Jorge Solórzano</member>
13241 <member>José Villanova</member>
13242 <member>Josef Šimánek</member>
13243 <member>Joseph Koshakow</member>
13244 <member>Julien Rouhaud</member>
13245 <member>Junwang Zhao</member>
13246 <member>Justin Pryzby</member>
13247 <member>Kaido Vaikla</member>
13248 <member>Kaimeh</member>
13249 <member>Karina Litskevich</member>
13250 <member>Karthik S</member>
13251 <member>Kartyshov Ivan</member>
13252 <member>Kashif Zeeshan</member>
13253 <member>Keisuke Kuroda</member>
13254 <member>Kevin Hale Boyes</member>
13255 <member>Kevin K Biju</member>
13256 <member>Kirill Reshke</member>
13257 <member>Kirill Zdornyy</member>
13258 <member>Koen De Groote</member>
13259 <member>Koichi Suzuki</member>
13260 <member>Koki Nakamura</member>
13261 <member>Konstantin Knizhnik</member>
13262 <member>Kouhei Sutou</member>
13263 <member>Kuntal Ghosh</member>
13264 <member>Kyotaro Horiguchi</member>
13265 <member>Lakshmi Narayana Velayudam</member>
13266 <member>Lars Kanis</member>
13267 <member>Laurence Parry</member>
13268 <member>Laurenz Albe</member>
13269 <member>Lele Gaifax</member>
13270 <member>Li Yong</member>
13271 <member>Lilian Ontowhee</member>
13272 <member>Lingbin Meng</member>
13273 <member>Luboslav Špilák</member>
13274 <member>Luca Vallisa</member>
13275 <member>Lukas Fittl</member>
13276 <member>Maciek Sakrejda</member>
13277 <member>Magnus Hagander</member>
13278 <member>Mahendra Singh Thalor</member>
13279 <member>Mahendrakar Srinivasarao</member>
13280 <member>Maiquel Grassi</member>
13281 <member>Maksim Korotkov</member>
13282 <member>Maksim Melnikov</member>
13283 <member>Man Zeng</member>
13284 <member>Marat Buharov</member>
13285 <member>Marc Balmer</member>
13286 <member>Marco Nenciarini</member>
13287 <member>Marcos Pegoraro</member>
13288 <member>Marina Polyakova</member>
13289 <member>Mark Callaghan</member>
13290 <member>Mark Dilger</member>
13291 <member>Marlene Brandstaetter</member>
13292 <member>Marlene Reiterer</member>
13293 <member>Martin Rakhmanov</member>
13294 <member>Masahiko Sawada</member>
13295 <member>Masahiro Ikeda</member>
13296 <member>Masao Fujii</member>
13297 <member>Mason Mackaman</member>
13298 <member>Mat Arye</member>
13299 <member>Matheus Alcantara</member>
13300 <member>Mats Kindahl</member>
13301 <member>Matthew Gabeler-Lee</member>
13302 <member>Matthew Kim</member>
13303 <member>Matthew Sterrett</member>
13304 <member>Matthew Woodcraft</member>
13305 <member>Matthias van de Meent</member>
13306 <member>Matthieu Denais</member>
13307 <member>Maurizio Boriani</member>
13308 <member>Max Johnson</member>
13309 <member>Max Madden</member>
13310 <member>Maxim Boguk</member>
13311 <member>Maxim Orlov</member>
13312 <member>Maximilian Chrzan</member>
13313 <member>Melanie Plageman</member>
13314 <member>Melih Mutlu</member>
13315 <member>Mert Alev</member>
13316 <member>Michael Banck</member>
13317 <member>Michael Bondarenko</member>
13318 <member>Michael Christofides</member>
13319 <member>Michael Guissine</member>
13320 <member>Michael Harris</member>
13321 <member>Michaël Paquier</member>
13322 <member>Michail Nikolaev</member>
13323 <member>Michal Kleczek</member>
13324 <member>Michel Pelletier</member>
13325 <member>Mikaël Gourlaouen</member>
13326 <member>Mikhail Gribkov</member>
13327 <member>Mikhail Kot</member>
13328 <member>Milosz Chmura</member>
13329 <member>Muralikrishna Bandaru</member>
13330 <member>Murat Efendioglu</member>
13331 <member>Mutaamba Maasha</member>
13332 <member>Naeem Akhter</member>
13333 <member>Nat Makarevitch</member>
13334 <member>Nathan Bossart</member>
13335 <member>Navneet Kumar</member>
13336 <member>Nazir Bilal Yavuz</member>
13337 <member>Neil Conway</member>
13338 <member>Niccolò Fei</member>
13339 <member>Nick Davies</member>
13340 <member>Nicolas Maus</member>
13341 <member>Niek Brasa</member>
13342 <member>Nikhil Raj</member>
13343 <member>Nikita</member>
13344 <member>Nikita Kalinin</member>
13345 <member>Nikita Malakhov</member>
13346 <member>Nikolay Samokhvalov</member>
13347 <member>Nikolay Shaplov</member>
13348 <member>Nisha Moond</member>
13349 <member>Nitin Jadhav</member>
13350 <member>Nitin Motiani</member>
13351 <member>Noah Misch</member>
13352 <member>Noboru Saito</member>
13353 <member>Noriyoshi Shinoda</member>
13354 <member>Ole Peder Brandtzæg</member>
13355 <member>Oleg Sibiryakov</member>
13356 <member>Oleg Tselebrovskiy</member>
13357 <member>Olleg Samoylov</member>
13358 <member>Onder Kalaci</member>
13359 <member>Ondrej Navratil</member>
13360 <member>Patrick Stählin</member>
13361 <member>Paul Amonson</member>
13362 <member>Paul Jungwirth</member>
13363 <member>Paul Ramsey</member>
13364 <member>Pavel Borisov</member>
13365 <member>Pavel Luzanov</member>
13366 <member>Pavel Nekrasov</member>
13367 <member>Pavel Stehule</member>
13368 <member>Peter Eisentraut</member>
13369 <member>Peter Geoghegan</member>
13370 <member>Peter Mittere</member>
13371 <member>Peter Smith</member>
13372 <member>Phil Eaton</member>
13373 <member>Philipp Salvisberg</member>
13374 <member>Philippe Beaudoin</member>
13375 <member>Pierre Giraud</member>
13376 <member>Pixian Shi</member>
13377 <member>Polina Bungina</member>
13378 <member>Przemyslaw Sztoch</member>
13379 <member>Quynh Tran</member>
13380 <member>Rafia Sabih</member>
13381 <member>Raghuveer Devulapalli</member>
13382 <member>Rahila Syed</member>
13383 <member>Rama Malladi</member>
13384 <member>Ran Benita</member>
13385 <member>Ranier Vilela</member>
13386 <member>Renan Alves Fonseca</member>
13387 <member>Richard Guo</member>
13388 <member>Richard Neill</member>
13389 <member>Rintaro Ikeda</member>
13390 <member>Robert Haas</member>
13391 <member>Robert Treat</member>
13392 <member>Robins Tharakan</member>
13393 <member>Roman Zharkov</member>
13394 <member>Ronald Cruz</member>
13395 <member>Ronan Dunklau</member>
13396 <member>Rui Zhao</member>
13397 <member>Rushabh Lathia</member>
13398 <member>Rustam Allakov</member>
13399 <member>Ryo Kanbayashi</member>
13400 <member>Ryohei Takahashi</member>
13401 <member>RyotaK</member>
13402 <member>Sagar Dilip Shedge</member>
13403 <member>Salvatore Dipietro</member>
13404 <member>Sam Gabrielsson</member>
13405 <member>Sam James</member>
13406 <member>Sameer Kumar</member>
13407 <member>Sami Imseih</member>
13408 <member>Samuel Thibault</member>
13409 <member>Satyanarayana Narlapuram</member>
13410 <member>Sebastian Skalacki</member>
13411 <member>Senglee Choi</member>
13412 <member>Sergei Kornilov</member>
13413 <member>Sergey Belyashov</member>
13414 <member>Sergey Dudoladov</member>
13415 <member>Sergey Prokhorenko</member>
13416 <member>Sergey Sargsyan</member>
13417 <member>Sergey Soloviev</member>
13418 <member>Sergey Tatarintsev</member>
13419 <member>Shaik Mohammad Mujeeb</member>
13420 <member>Shawn McCoy</member>
13421 <member>Shenhao Wang</member>
13422 <member>Shihao Zhong</member>
13423 <member>Shinya Kato</member>
13424 <member>Shlok Kyal</member>
13425 <member>Shubham Khanna</member>
13426 <member>Shveta Malik</member>
13427 <member>Simon Riggs</member>
13428 <member>Smolkin Grigory</member>
13429 <member>Sofia Kopikova</member>
13430 <member>Song Hongyu</member>
13431 <member>Song Jinzhou</member>
13432 <member>Soumyadeep Chakraborty</member>
13433 <member>Sravan Kumar</member>
13434 <member>Srinath Reddy</member>
13435 <member>Stan Hu</member>
13436 <member>Stepan Neretin</member>
13437 <member>Stephen Fewer</member>
13438 <member>Stephen Frost</member>
13439 <member>Steve Chavez</member>
13440 <member>Steven Niu</member>
13441 <member>Suraj Kharage</member>
13442 <member>Sven Klemm</member>
13443 <member>Takamichi Osumi</member>
13444 <member>Takeshi Ideriha</member>
13445 <member>Tatsuo Ishii</member>
13446 <member>Ted Yu</member>
13447 <member>Tels</member>
13448 <member>Tender Wang</member>
13449 <member>Teodor Sigaev</member>
13450 <member>Thom Brown</member>
13451 <member>Thomas Baehler</member>
13452 <member>Thomas Krennwallner</member>
13453 <member>Thomas Munro</member>
13454 <member>Tim Wood</member>
13455 <member>Timur Magomedov</member>
13456 <member>Tobias Wendorff</member>
13457 <member>Todd Cook</member>
13458 <member>Tofig Aliev</member>
13459 <member>Tom Lane</member>
13460 <member>Tomas Vondra</member>
13461 <member>Tomasz Rybak</member>
13462 <member>Tomasz Szypowski</member>
13463 <member>Torsten Foertsch</member>
13464 <member>Toshi Harada</member>
13465 <member>Tristan Partin</member>
13466 <member>Triveni N</member>
13467 <member>Umar Hayat</member>
13468 <member>Vallimaharajan G</member>
13469 <member>Vasya Boytsov</member>
13470 <member>Victor Yegorov</member>
13471 <member>Vignesh C</member>
13472 <member>Viktor Holmberg</member>
13473 <member>Vinícius Abrahão</member>
13474 <member>Vinod Sridharan</member>
13475 <member>Virender Singla</member>
13476 <member>Vitaly Davydov</member>
13477 <member>Vladlen Popolitov</member>
13478 <member>Vladyslav Nebozhyn</member>
13479 <member>Walid Ibrahim</member>
13480 <member>Webbo Han</member>
13481 <member>Wenhui Qiu</member>
13482 <member>Will Mortensen</member>
13483 <member>Will Storey</member>
13484 <member>Wolfgang Walther</member>
13485 <member>Xin Zhang</member>
13486 <member>Xing Guo</member>
13487 <member>Xuneng Zhou</member>
13488 <member>Yan Chengpen</member>
13489 <member>Yang Lei</member>
13490 <member>Yaroslav Saburov</member>
13491 <member>Yaroslav Syrytsia</member>
13492 <member>Yasir Hussain</member>
13493 <member>Yasuo Honda</member>
13494 <member>Yogesh Sharma</member>
13495 <member>Yonghao Lee</member>
13496 <member>Yoran Heling</member>
13497 <member>Yu Liang</member>
13498 <member>Yugo Nagata</member>
13499 <member>Yuhang Qiu</member>
13500 <member>Yuki Seino</member>
13501 <member>Yura Sokolov</member>
13502 <member>Yurii Rashkovskii</member>
13503 <member>Yushi Ogiwara</member>
13504 <member>Yusuke Sugie</member>
13505 <member>Yuta Katsuragi</member>
13506 <member>Yuto Sasaki</member>
13507 <member>Yuuki Fujii</member>
13508 <member>Yuya Watari</member>
13509 <member>Zane Duffield</member>
13510 <member>Zeyuan Hu</member>
13511 <member>Zhang Mingli</member>
13512 <member>Zhihong Yu</member>
13513 <member>Zhijie Hou</member>
13514 <member>Zsolt Parragi</member>
13515 </simplelist>
13516 </sect2>
13517
13518 </sect1>