+ A dump/restore is not required for those running 13.X.
+ However, if you have applied REINDEX CONCURRENTLY to a TOAST table's
index, or observe failures to access TOAST datums, there has been a
fix for this problem. Any existing corrupted indexes can be repaired
by reindexing again.
+ Also, if you are upgrading from a version earlier than 13.5,
see those release notes as well please.
This bug was fixed in the package postgresql-13 - 13.6-0ubuntu0. 21.10.1
--------------- 21.10.1) impish; urgency=medium
postgresql-13 (13.6-0ubuntu0.
* New upstream version (LP: #1961127).
+ A dump/restore is not required for those running 13.X.
+ However, if you have applied REINDEX CONCURRENTLY to a TOAST table's
index, or observe failures to access TOAST datums, there has been a
fix for this problem. Any existing corrupted indexes can be repaired
by reindexing again.
+ Also, if you are upgrading from a version earlier than 13.5,
see those release notes as well please.
+ Details about these and many further changes can be found at: /www.postgresql .org/docs/ 13/release- 13-6.html
https:/
-- Sergio Durigan Junior <email address hidden> Wed, 16 Feb 2022 21:17:27 -0500