]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Always call ExecShutdownNode() if appropriate.
authorThomas Munro <tmunro@postgresql.org>
Fri, 15 Nov 2019 21:04:52 +0000 (10:04 +1300)
committerThomas Munro <tmunro@postgresql.org>
Fri, 15 Nov 2019 21:18:45 +0000 (10:18 +1300)
commit24897e1a1af27dc759fb41afba2a663ff9af4ef6
tree0fd91e68c362144faf9610a7b457ad48783d27a6
parentd61e7f174db9ee45df58afc103682d933048aa9a
Always call ExecShutdownNode() if appropriate.

Call ExecShutdownNode() after ExecutePlan()'s loop, rather than at each
break.  We had forgotten to do that in one case.  The omission caused
intermittent "temporary file leak" warnings from multi-batch parallel
hash joins with a LIMIT clause.

Back-patch to 11.  Though the problem exists in theory in earlier
parallel query releases, nothing really depended on it.

Author: Kyotaro Horiguchi
Reviewed-by: Thomas Munro, Amit Kapila
Discussion: https://postgr.es/m/20191111.212418.2222262873417235945.horikyota.ntt%40gmail.com
src/backend/executor/execMain.c