From 321c87e5ca1a8a766a55ec4201099a37b9b0c68b 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/include/nodes/relation.h | 1 + 1 file changed, 1 insertion(+) (limited to 'src/include/nodes/relation.h') diff --git a/src/include/nodes/relation.h b/src/include/nodes/relation.h index f9b4067b1e7..3c7436cf27e 100644 --- a/src/include/nodes/relation.h +++ b/src/include/nodes/relation.h @@ -674,6 +674,7 @@ typedef struct IndexOptInfo bool amhasgettuple; /* does AM have amgettuple interface? */ bool amhasgetbitmap; /* does AM have amgetbitmap interface? */ bool amcanparallel; /* does AM support parallel scan? */ + bool amcanmarkpos; /* does AM support mark/restore? */ /* Rather than include amapi.h here, we declare amcostestimate like this */ void (*amcostestimate) (); /* AM's cost estimator */ } IndexOptInfo; -- cgit v1.2.3