Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add guc gp_enable_explain_motion_detail to show sender time when Expl… #352

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

songdongxiaoa2
Copy link
Contributor

@songdongxiaoa2 songdongxiaoa2 commented Dec 29, 2023

Show motion sender time when Explain Analyse.

When guc set, Explain Analyse result will be:
actual time=<receive_start>..<receive_end>/<sender_start>..<sender_end>

gp_enable_explain_motion_detail defaults to off.


Change logs

QEs will now send Motion Sender instruments to QD.
QD will collect two instruments(sender and receiver) to MotionPlanState->instruments[].
Add guc gp_enable_explain_motion_detail to show sender time.
Add test cases.

Why are the changes needed?

In plan on QD, Motion is a single node, so we need an array of two to collect both sender and receiver instruments.
Add guc to show this information only when needed.

Does this PR introduce any user-facing change?

Yes, the guc gp_enable_explain_motion_detail default to off. Show sending time by:
set gp_enable_explain_motion_detail to on
in client.

How was this patch tested?

Added icw test case and passed in local.

Contributor's Checklist

…ain Analyse.

gp_enable_explain_motion_detail default to off.

Signed-off-by: Dongxiao Song <songdongxiao@hashdata.cn>
@CLAassistant
Copy link

CLAassistant commented Dec 29, 2023

CLA assistant check
All committers have signed the CLA.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hiiii, @songdongxiaoa2 welcome!🎊 Thanks for taking the effort to make our project better! 🙌 Keep making such awesome contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants