Import Always call ExecShutdownNode() if appropriate. #8183
Comments
tedyu
added a commit
that referenced
this issue
Apr 28, 2021
Summary: Commit was bc049d0d460aead528ace909a3477bc701ab2e9a Commit message was: ``` 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 ``` Test Plan: Build yugabyte db and run test suite via Jenkins Reviewers: neil, jason Reviewed By: jason Subscribers: yql Differential Revision: https://phabricator.dev.yugabyte.com/D11370
YintongMa
pushed a commit
to YintongMa/yugabyte-db
that referenced
this issue
May 26, 2021
…riate. Summary: Commit was bc049d0d460aead528ace909a3477bc701ab2e9a Commit message was: ``` 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 ``` Test Plan: Build yugabyte db and run test suite via Jenkins Reviewers: neil, jason Reviewed By: jason Subscribers: yql Differential Revision: https://phabricator.dev.yugabyte.com/D11370
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Commit was bc049d0d460aead528ace909a3477bc701ab2e9a
The text was updated successfully, but these errors were encountered: