From 660b89928d18386de7755565c008439ae75d1218 Mon Sep 17 00:00:00 2001 From: Andrew Gierth Date: Tue, 24 Nov 2020 20:58:32 +0000 Subject: Properly check index mark/restore in ExecSupportsMarkRestore. Previously this code assumed that all IndexScan nodes supported mark/restore, which is not true since it depends on optional index AM support functions. This could lead to errors about missing support functions in rare edge cases of mergejoins with no sort keys, where an unordered non-btree index scan was placed on the inner path without a protecting Materialize node. (Normally, the fact that merge join requires ordered input would avoid this error.) Backpatch all the way since this bug is ancient. Per report from Eugen Konkov on irc. Discussion: https://postgr.es/m/87o8jn50be.fsf@news-spur.riddles.org.uk --- src/backend/executor/execAmi.c | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'src/backend/executor') diff --git a/src/backend/executor/execAmi.c b/src/backend/executor/execAmi.c index e2154ba86aa..0c10f1d35c2 100644 --- a/src/backend/executor/execAmi.c +++ b/src/backend/executor/execAmi.c @@ -417,6 +417,11 @@ ExecSupportsMarkRestore(Path *pathnode) { case T_IndexScan: case T_IndexOnlyScan: + /* + * Not all index types support mark/restore. + */ + return castNode(IndexPath, pathnode)->indexinfo->amcanmarkpos; + case T_Material: case T_Sort: return true; -- cgit v1.2.3