GitHub user liming01 opened a pull request:
https://github.com/apache/incubator-hawq/pull/1222
HAWQ-1438. Support resource owner beyond transaction boundary
(1) Add TopResourceOwner to trace resource used beyond the transaction
boundary.
(2) When to auto alloc a new TopResourceOwner for each process?
Generate a singleton TopResourceOwner when setting CurrentResourceOwner
to NULL.
(3) If crashed at some code beyond the transaction boundary, we should
manually create
a new resource owner, because we do manually create a new one for each
process.
(4) When to call ResourceOwnerDelete(TopResourceOwner) automatically for
each process?
Register it at on_proc_exit().
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/liming01/incubator-hawq mli/resownerOutTx
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/1222.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1222
----
commit 049f5ff6c0f98b4b7224d97b5b926a58a06cce54
Author: Ming LI <m...@apache.org>
Date: 2017-04-20T09:04:51Z
HAWQ-1438. Support resource owner beyond transaction boundary
(1) Add TopResourceOwner to trace resource used beyond the transaction
boundary.
(2) When to auto alloc a new TopResourceOwner for each process?
Generate a singleton TopResourceOwner when setting CurrentResourceOwner
to NULL.
(3) If crashed at some code beyond the transaction boundary, we should
manually create
a new resource owner, because we do manually create a new one for each
process.
(4) When to call ResourceOwnerDelete(TopResourceOwner) automatically for
each process?
Register it at on_proc_exit().
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
