diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-09-01 17:38:54 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-09-01 17:39:01 -0400 |
| commit | 51daa7bdb39e1bdc31eb99fd3f54f61743ebb7ae (patch) | |
| tree | a527c43c5129b7f154b32326337e062202c04010 /contrib/btree_gist/btree_gist.c | |
| parent | c039ba0716383ccaf88c9be1a7f0803a77823de1 (diff) | |
| download | postgresql-51daa7bdb39e1bdc31eb99fd3f54f61743ebb7ae.tar.gz postgresql-51daa7bdb39e1bdc31eb99fd3f54f61743ebb7ae.zip | |
Improve division of labor between execParallel.c and nodeGather[Merge].c.
Move the responsibility for creating/destroying TupleQueueReaders into
execParallel.c, to avoid duplicative coding in nodeGather.c and
nodeGatherMerge.c. Also, instead of having DestroyTupleQueueReader do
shm_mq_detach, do it in the caller (which is now only ExecParallelFinish).
This means execParallel.c does both the attaching and detaching of the
tuple-queue-reader shm_mqs, which seems less weird than the previous
arrangement.
These changes also eliminate a vestigial memory leak (of the pei->tqueue
array). It's now demonstrable that rescans of Gather or GatherMerge don't
leak memory.
Discussion: https://postgr.es/m/8670.1504192177@sss.pgh.pa.us
Diffstat (limited to 'contrib/btree_gist/btree_gist.c')
0 files changed, 0 insertions, 0 deletions