mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-02-23 19:39:53 +08:00
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
This commit is contained in:
parent
c442722648
commit
9155b4be9a
@ -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;
|
||||
|
Loading…
Reference in New Issue
Block a user