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
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/9155b4be9a13038d59a7a09a27b7fbce3819eb08
Modified Files
--------------
src/backend/executor/nodeIncrementalSort.c | 1 -
1 file changed, 1 deletion(-)
