diff --git a/doc/src/sgml/release-14.sgml b/doc/src/sgml/release-14.sgml
index 82f961d228..d824d2d888 100644
--- a/doc/src/sgml/release-14.sgml
+++ b/doc/src/sgml/release-14.sgml
@@ -42,29 +42,6 @@
-
- Fix corruption of HOT chains when a RECENTLY_DEAD tuple changes
- state to fully DEAD during page pruning (Andres Freund)
-
-
-
- This happens when the last transaction that could see
- the tuple ends while the page is being pruned. It was then possible
- to remove a tuple that is pointed to by a redirect item elsewhere on
- the page. While that causes no immediate problem, when the item slot
- is re-used by some new tuple, that tuple would be thought to be part
- of the pre-existing HOT chain, creating a form of index corruption.
- If this seems to have affected a table, REINDEX
- should repair the damage.
-
-
-
-
-
+
+ Fix corruption of HOT chains when a RECENTLY_DEAD tuple changes
+ state to fully DEAD during page pruning (Andres Freund)
+
+
+
+ It was possible for VACUUM to remove a
+ recently-dead tuple while leaving behind a redirect item that
+ pointed to it. When the tuple's item slot is later re-used by
+ some new tuple, that tuple would be seen as part of the
+ pre-existing HOT chain, creating a form of index corruption.
+ If this has happened, reindexing the table should repair the
+ damage. However, this is an extremely low-probability scenario,
+ so we do not recommend reindexing just on the chance that it might
+ have happened.
+
+
+
+
+
- Fix failure of SP-GiST indexes when indexed column's data type is
- binary-compatible with the declared input type of the operator class
- (Tom Lane)
+ Fix failure of SP-GiST indexes when the indexed column's data type
+ is binary-compatible with the declared input type of the operator
+ class (Tom Lane)
@@ -848,7 +849,7 @@ Branch: REL_10_STABLE [3bc46e4e9] 2021-11-12 14:55:32 -0500
This agrees with the documented behavior, and avoids probable
permissions failure if SET ROLE or SET
SESSION AUTHORIZATION has been done since the session began.
- To reduce confusion, the role name to be acted on is now always
+ To prevent confusion, the role name to be acted on is now
included in the password prompt.
@@ -1052,14 +1053,14 @@ Branch: REL_10_STABLE [b21986908] 2022-01-08 14:54:39 -0500
Index-only scans returned column values with trailing spaces
- removed, which is not the expected behavior. That happens because
- that's how it's stored in the index. This fix changes the logic to
- store char(N) values with
- the expected amount of space padding. The behavior of the index
- will not change immediately unless you REINDEX
- it; otherwise space-stripped values will be gradually replaced over
- time during updates. Queries that do not use index-only scan plans
- will be unaffected in any case.
+ removed, which is not the expected behavior. That happened because
+ that's how the data was stored in the index. This fix changes the
+ code to store char(N) values
+ with the expected amount of space padding.
+ The behavior of such an index will not change immediately unless
+ you REINDEX it; otherwise space-stripped values
+ will be gradually replaced over time during updates. Queries that
+ do not use index-only scan plans will be unaffected in any case.