NotificationsYou must be signed in to change notification settings
Fork28
Star151

Commit9155b4b

committed

Do no reset bounded before incremental sort rescan

ExecReScanIncrementalSort was resetting bounded=false, which means theoptimization would be disabled on all rescans. This happens becauseExecSetTupleBound is called before the rescan, not after it.Author: James ColemanReviewed-by: Tomas VondraDiscussion:https://postgr.es/m/20200414065336.GI1492@paquier.xyz

1 parentc442722 commit9155b4bCopy full SHA for 9155b4b

File tree

1 file changed

-1

lines changed

src/backend/executor
- nodeIncrementalSort.c

1 file changed

-1

lines changed

`‎src/backend/executor/nodeIncrementalSort.c`

Lines changed: 0 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1142,7 +1142,6 @@ ExecReScanIncrementalSort(IncrementalSortState *node)`
`1142`	`1142`	`if (node->transfer_tuple!=NULL)`
`1143`	`1143`	`ExecClearTuple(node->transfer_tuple);`
`1144`	`1144`
`1145`		`-node->bounded= false;`
`1146`	`1145`	`node->outerNodeDone= false;`
`1147`	`1146`	`node->n_fullsort_remaining=0;`
`1148`	`1147`	`node->bound_Done=0;`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit9155b4b

File tree

1 file changed

1 file changed

`‎src/backend/executor/nodeIncrementalSort.c`

0 commit comments