postgres.git / summary / log / commit / refs

commit    b6608ae5d3cc16005d4fd4f1be2790e3ad566892
Author:   Peter Geoghegan <pg@bowt.ie>
Date:     Wed Jul 29 23:00:48 2020 +0000
First released in: 9.5.23, 9.6.19, 10.14, 11.9

    Backpatch tuplesort.c assertion.
    
    Backpatch an assertion (that was originally added to Postgres 12 by
    commit dd299df8189) that seems broadly useful.  The assertion can detect
    violations of the HOT invariant (i.e. no two index tuples can point to
    the same heap TID) when CREATE INDEX somehow incorrectly allows that to
    take place.
    
    For example, a IndexBuildHeapScan/heapam_index_build_range_scan bug
    might result in two tuples that both point to the same heap TID.  If
    these two tuples also happen to be duplicates, the assertion will fail.
    
    Discussion: https://postgr.es/m/CAH2-WzmBxu4o=pMsniur+bwHqCGCmV_AOLkuK6BuU7ngA6evqw@mail.gmail.com
    Backpatch: 9.5-11 only


 src/backend/utils/sort/tuplesort.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/backend/utils/sort/tuplesort.c b/src/backend/utils/sort/tuplesort.c
index b6951d4ac93..1a7a08ea946 100644
--- a/src/backend/utils/sort/tuplesort.c
+++ b/src/backend/utils/sort/tuplesort.c
@@ -3682,6 +3682,9 @@ comparetup_index_btree(const SortTuple *a, const SortTuple *b,
 			return (pos1 < pos2) ? -1 : 1;
 	}
 
+	/* ItemPointer values should never be equal */
+	Assert(false);
+
 	return 0;
 }
 
@@ -3731,6 +3734,9 @@ comparetup_index_hash(const SortTuple *a, const SortTuple *b,
 			return (pos1 < pos2) ? -1 : 1;
 	}
 
+	/* ItemPointer values should never be equal */
+	Assert(false);
+
 	return 0;
 }
 


[parent: aaa132a65deb]