diff --git a/doc/src/sgml/release-14.sgml b/doc/src/sgml/release-14.sgml
index d95734e91f..0b5ed12817 100644
--- a/doc/src/sgml/release-14.sgml
+++ b/doc/src/sgml/release-14.sgml
@@ -409,7 +409,7 @@ Branch: REL_11_STABLE [0d08c279b] 2021-10-19 13:54:46 -0400
A command such as UPDATE tab SET fld[1].subfld =
- value failed if the array elements were domains rather
+ val failed if the array's elements were domains rather
than plain composites.
@@ -427,9 +427,9 @@ Branch: REL_13_STABLE [170206e45] 2021-10-01 18:29:18 -0300
- FETCH FIRST WITH TIES necessarily fetches
- one more row than requested, so tha it can determine whether the
- next row is a tie or not. In our current implementation,
+ FETCH FIRST WITH TIES necessarily fetches one
+ more row than requested, since it cannot stop until it finds a row
+ that is not a tie. In our current implementation,
if FOR UPDATE is used then that row will also get
locked even though it is not returned. That results in undesirable
behavior if the SKIP LOCKED option is specified.
@@ -454,9 +454,9 @@ Branch: REL_10_STABLE [5d7c6b6c8] 2021-09-03 16:38:55 -0400
- Previously this was allowed, but the collation effectively vanished
- into the ether because of the way collation lookup works: you could
- not use the collation, nor even drop it.
+ Previously this was allowed, but then the collation could not be
+ referenced because of the way collation lookup works; you could not
+ use the collation, nor even drop it.
@@ -473,7 +473,7 @@ Branch: REL_13_STABLE [85dc4292a] 2021-10-19 11:04:04 +0900
- While the parser accepts this, it's undocumented and doesn't
+ While the parser accepted this, it's undocumented and doesn't
actually work.
@@ -545,7 +545,7 @@ Branch: REL9_6_STABLE [d90e14414] 2021-08-23 17:41:07 -0400
The regexp engine was careless about clearing match data
for capturing parentheses after rejecting a partial match. This
- could allow a later back-reference to succeed when by rights it
+ could allow a later back-reference to match in places where it
should fail for lack of a defined referent.
@@ -567,10 +567,9 @@ Branch: REL9_6_STABLE [cafebd663] 2021-08-20 14:19:04 -0400
- Unnecessarily stupid back-tracking logic could result in exponential
- time spent looking for a match. Fortunately the problem is masked
- in most cases by other optimizations; but it is possible to
- demonstrate it with fairly simple, if contrived, regexps.
+ Incorrect back-tracking logic could result in exponential time spent
+ looking for a match. Fortunately the problem is masked in most
+ cases by other optimizations.
@@ -599,49 +598,6 @@ Branch: REL9_6_STABLE [5907c3818] 2021-09-06 11:29:52 -0400
-
- Use the CLDR project's data to map Windows time zone names to IANA
- time zones (Tom Lane)
-
-
-
- When running on Windows, initdb attempts
- to set the new cluster's timezone parameter to
- the IANA time zone matching the system's prevailing time zone.
- We were using a mapping table that we'd generated years ago and
- updated only fitfully; unsurprisingly, it contained a number of
- errors as well as omissions of recently-added zones. It turns out
- that CLDR has been tracking the most appropriate mappings, so start
- using their data. This change will not affect any existing
- installation, only newly-initialized clusters.
-
-
-
-
-
- Ensure prepared transactions are properly accounted for during
+ Ensure that prepared transactions are properly accounted for during
promotion of a standby server (Michael Paquier, Andres Freund)
@@ -959,7 +915,8 @@ Branch: REL_10_STABLE [96f6ef9fe] 2021-08-25 08:55:52 -0400
This oversight could lead to misbehavior in parallel queries if the
- transaction isolation level is less than REPEATABLE READ.
+ transaction isolation level is less than REPEATABLE
+ READ.
@@ -1011,14 +968,14 @@ Branch: REL_10_STABLE [f77489046] 2021-09-09 23:59:40 +0900
Branch: REL9_6_STABLE [61e2aa2db] 2021-09-10 00:00:06 +0900
-->
- Fix walreceiver to ensure that it creates an archive notification
- file before exiting (Fujii Masao)
+ Ensure that walreceiver processes create all required archive
+ notification files before exiting (Fujii Masao)
- This failed to happen if the walreceiver exited exactly at a WAL
- segment boundary, thus delaying archiving of the new segment on the
- standby.
+ If a walreceiver exited exactly at a WAL segment boundary, it failed
+ to make a notification file for the last-received segment, thus
+ delaying archiving of that segment on the standby.
@@ -1033,8 +990,8 @@ Branch: REL_14_STABLE [ae254356f] 2021-10-06 13:28:30 +0900
Branch: REL_13_STABLE [d6d68e223] 2021-10-06 13:28:35 +0900
-->
- Compute the correct WAL range to include in a backup manifest when a
- timeline change is involved (Kyotaro Horiguchi)
+ Fix computation of the WAL range to include in a backup manifest
+ when a timeline change is involved (Kyotaro Horiguchi)
@@ -1095,8 +1052,8 @@ Branch: REL_13_STABLE [a73a3671d] 2021-10-20 13:05:42 -0300
Branch: REL_12_STABLE [3c8c49945] 2021-10-20 13:05:42 -0300
-->
- Ensure correct lock level is used when renaming a table (Nathan
- Bossart, Álvaro Herrera)
+ Ensure that the correct lock level is used when renaming a table
+ (Nathan Bossart, Álvaro Herrera)
@@ -1267,7 +1224,7 @@ Branch: REL_10_STABLE [4874886b4] 2021-08-13 16:44:18 +1200
- It seems unlikely that this bug has yet been hit in practice, as it
+ It seems unlikely that this bug has been hit in practice, as it
would require work_mem settings of hundreds of
gigabytes for existing uses of simplehash.h.
@@ -1348,6 +1305,23 @@ Branch: REL_13_STABLE [d5a2ffbce] 2021-10-27 13:09:00 -0700
+
+ Avoid assertion failure when inserting NaN into a BRIN
+ float8 or float4 minmax_multi_ops index (Tomas Vondra)
+
+
+
+ In production builds, such cases would result in a somewhat
+ inefficient, but not actually incorrect, index.
+
+
+
+
+
+
+ Use the CLDR project's data to map Windows time zone names to IANA
+ time zones (Tom Lane)
+
+
+
+ When running on Windows, initdb attempts
+ to set the new cluster's timezone parameter to
+ the IANA time zone matching the system's prevailing time zone.
+ We were using a mapping table that we'd generated years ago and
+ updated only fitfully; unsurprisingly, it contained a number of
+ errors as well as omissions of recently-added zones. It turns out
+ that CLDR has been tracking the most appropriate mappings, so start
+ using their data. This change will not affect any existing
+ installation, only newly-initialized clusters.
+
+
+
+
+