-
- Downloads
Adjust scan plan nodes to avoid getting an extra AccessShareLock on a
relation if it's already been locked by execMain.c as either a result relation or a FOR UPDATE/SHARE relation. This avoids an extra trip to the shared lock manager state. Per my suggestion yesterday.
Showing
- src/backend/executor/execMain.c 7 additions, 14 deletionssrc/backend/executor/execMain.c
- src/backend/executor/execUtils.c 90 additions, 2 deletionssrc/backend/executor/execUtils.c
- src/backend/executor/nodeBitmapHeapscan.c 7 additions, 19 deletionssrc/backend/executor/nodeBitmapHeapscan.c
- src/backend/executor/nodeBitmapIndexscan.c 3 additions, 3 deletionssrc/backend/executor/nodeBitmapIndexscan.c
- src/backend/executor/nodeIndexscan.c 5 additions, 16 deletionssrc/backend/executor/nodeIndexscan.c
- src/backend/executor/nodeSeqscan.c 5 additions, 19 deletionssrc/backend/executor/nodeSeqscan.c
- src/backend/executor/nodeTidscan.c 4 additions, 17 deletionssrc/backend/executor/nodeTidscan.c
- src/include/executor/executor.h 4 additions, 1 deletionsrc/include/executor/executor.h
- src/include/nodes/execnodes.h 10 additions, 1 deletionsrc/include/nodes/execnodes.h
Loading
Please register or sign in to comment