-
Notifications
You must be signed in to change notification settings - Fork 125
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 function cbdb_relation_size #428
Conversation
It can be used to fetch the size of a batch of relations as below SELECT * FROM cbdb_relation_size((SELECT array_agg(oid) FROM pg_class)); it has better perfomance than pg_relation_size in such case, more details see the comment on the function
Xiaoran Wang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hiiii, @fanfuxiaoran welcome!🎊 Thanks for taking the effort to make our project better! 🙌 Keep making such awesome contributions!
And move getting forkNumber into SRF_IS_FIRSTCALL to avoid warning.
Add function cbdb_relation_size It can be used to fetch the size of a batch of relations as below SELECT * FROM cbdb_relation_size((SELECT array_agg(oid) FROM pg_class)); It has better performance than pg_relation_size in such case, more details see the comment on the function Co-authored-by: Xiaoran Wang <wangxiaoran@hashdata.cn> (cherry picked from commit 27dc124)
It can be used to fetch the size of a batch
of relations as below
SELECT * FROM
cbdb_relation_size((SELECT array_agg(oid) FROM pg_class));
it has better perfomance than pg_relation_size
in such case, more details see the comment on
the function
fix #ISSUE_Number
Change logs
Describe your change clearly, including what problem is being solved or what feature is being added.
If it has some breaking backward or forward compatibility, please clary.
Why are the changes needed?
Describe why the changes are necessary.
Does this PR introduce any user-facing change?
If yes, please clarify the previous behavior and the change this PR proposes.
How was this patch tested?
Please detail how the changes were tested, including manual tests and any relevant unit or integration tests.
Contributor's Checklist
Here are some reminders and checklists before/when submitting your pull request, please check them:
make installcheck
make -C src/test installcheck-cbdb-parallel
cloudberrydb/dev
team for review and approval when your PR is ready🥳