-
- Downloads
Be more tense about not creating tuplestores with randomAccess = true unless
backwards scan could actually happen. In particular, pass a flag to materialize-mode SRFs that tells them whether they need to require random access. In passing, also suppress unneeded backward-scan overhead for a Portal's holdStore tuplestore. Per my proposal about reducing I/O costs for tuplestores.
Showing
- contrib/tablefunc/tablefunc.c 14 additions, 7 deletionscontrib/tablefunc/tablefunc.c
- contrib/xml2/xpath.c 4 additions, 2 deletionscontrib/xml2/xpath.c
- src/backend/commands/prepare.c 4 additions, 2 deletionssrc/backend/commands/prepare.c
- src/backend/executor/execQual.c 8 additions, 4 deletionssrc/backend/executor/execQual.c
- src/backend/executor/nodeFunctionscan.c 4 additions, 2 deletionssrc/backend/executor/nodeFunctionscan.c
- src/backend/utils/fmgr/README 5 additions, 1 deletionsrc/backend/utils/fmgr/README
- src/backend/utils/mmgr/portalmem.c 13 additions, 5 deletionssrc/backend/utils/mmgr/portalmem.c
- src/include/executor/executor.h 3 additions, 2 deletionssrc/include/executor/executor.h
- src/include/nodes/execnodes.h 5 additions, 2 deletionssrc/include/nodes/execnodes.h
- src/pl/plperl/plperl.c 3 additions, 2 deletionssrc/pl/plperl/plperl.c
- src/pl/plpgsql/src/pl_exec.c 4 additions, 2 deletionssrc/pl/plpgsql/src/pl_exec.c
Loading
Please register or sign in to comment