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:11:30 +0000 (10:11 +1300)
commit76cbfcdf3a0dff3f029ca079701418b861ce86c8
treec27cea514c518fc8d603bf0ec87f3e5c99c70d77
parent6ae4d271879b62c4325df3ddf75bff3f2b911086
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