From 9155b4be9a13038d59a7a09a27b7fbce3819eb08 Mon Sep 17 00:00:00 2001 From: Tomas Vondra Date: Sat, 9 May 2020 19:41:36 +0200 Subject: [PATCH] Do no reset bounded before incremental sort rescan ExecReScanIncrementalSort was resetting bounded=false, which means the optimization would be disabled on all rescans. This happens because ExecSetTupleBound is called before the rescan, not after it. Author: James Coleman Reviewed-by: Tomas Vondra Discussion: https://postgr.es/m/20200414065336.GI1492@paquier.xyz --- src/backend/executor/nodeIncrementalSort.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/backend/executor/nodeIncrementalSort.c b/src/backend/executor/nodeIncrementalSort.c index ae7ad5d7bd..bfc2e4cf6b 100644 --- a/src/backend/executor/nodeIncrementalSort.c +++ b/src/backend/executor/nodeIncrementalSort.c @@ -1142,7 +1142,6 @@ ExecReScanIncrementalSort(IncrementalSortState *node) if (node->transfer_tuple != NULL) ExecClearTuple(node->transfer_tuple); - node->bounded = false; node->outerNodeDone = false; node->n_fullsort_remaining = 0; node->bound_Done = 0;