During heap rebuild, lock any TOAST index until end of transaction.

swap_relation_files() calls toast_get_valid_index() to find and lock
this index, just before swapping with the rebuilt TOAST index.  The
latter function releases the lock before returning.  Potential for
mischief is low; a concurrent session can issue ALTER INDEX ... SET
(fillfactor = ...), which is not alarming.  Nonetheless, changing
pg_class.relfilenode without a lock is unconventional.  Back-patch to
9.5 (all supported versions), because another fix needs this.

Discussion: https://postgr.es/m/20191226001521.GA1772687@rfd.leadboat.com

diff --git a/src/backend/access/common/toast_internals.c b/src/backend/access/common/toast_internals.c
index 65801a2a840843843499953fbc619f75d7754175..25a81e5ec655d3e3a7cd19a4caecef305a8551d5 100644 (file)
--- a/src/backend/access/common/toast_internals.c
+++ b/src/backend/access/common/toast_internals.c
@@ -528,8 +528,8 @@ toast_get_valid_index(Oid toastoid, LOCKMODE lock)
    validIndexOid = RelationGetRelid(toastidxs[validIndex]);
 
    /* Close the toast relation and all its indexes */
-   toast_close_indexes(toastidxs, num_indexes, lock);
-   table_close(toastrel, lock);
+   toast_close_indexes(toastidxs, num_indexes, NoLock);
+   table_close(toastrel, NoLock);
 
    return validIndexOid;
 }

diff --git a/src/backend/commands/cluster.c b/src/backend/commands/cluster.c
index 11ce1bb40468084cd14568003a1a0b7a96a27673..fc1cea0236a10f7b8b4be94402a0662e27fce765 100644 (file)
--- a/src/backend/commands/cluster.c
+++ b/src/backend/commands/cluster.c
@@ -1489,7 +1489,7 @@ finish_heap_swap(Oid OIDOldHeap, Oid OIDNewHeap,
 
            /* Get the associated valid index to be renamed */
            toastidx = toast_get_valid_index(newrel->rd_rel->reltoastrelid,
-                                            AccessShareLock);
+                                            NoLock);
 
            /* rename the toast table ... */
            snprintf(NewToastName, NAMEDATALEN, "pg_toast_%u",