diff options
| author | Tomas Vondra <tomas.vondra@postgresql.org> | 2020-05-09 19:41:36 +0200 |
|---|---|---|
| committer | Tomas Vondra <tomas.vondra@postgresql.org> | 2020-05-09 19:41:36 +0200 |
| commit | 9155b4be9a13038d59a7a09a27b7fbce3819eb08 (patch) | |
| tree | f7b0d67574639e59721e2b28cc24854aaeb497d9 /src/backend/executor/nodeIncrementalSort.c | |
| parent | c4427226483c78618ba45eff34917400a77718a5 (diff) | |
| download | postgresql-9155b4be9a13038d59a7a09a27b7fbce3819eb08.tar.gz postgresql-9155b4be9a13038d59a7a09a27b7fbce3819eb08.zip | |
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
Diffstat (limited to 'src/backend/executor/nodeIncrementalSort.c')
| -rw-r--r-- | src/backend/executor/nodeIncrementalSort.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/backend/executor/nodeIncrementalSort.c b/src/backend/executor/nodeIncrementalSort.c index ae7ad5d7bde..bfc2e4cf6b1 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; |