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

Fix test output plan verification (#2021) #2065

Conversation

rohit01010
Copy link
Contributor

@rohit01010 rohit01010 commented Nov 24, 2023

Description

Test BABEL-4281 gives the memory usage with STATISTICS PROFILE. During testing, this value can change, causing test failures. Switching to SHOWPLAN_ALL will give a plan without outputing memory usage.

Cherry-picked from PR-2021

Authored-by: Walt Boettge [email protected]
Signed-off-by: Rohit Bhagat [email protected]

Check List

  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.

wboettge and others added 2 commits November 24, 2023 08:23
Test BABEL-4281 gives the memory usage with STATISTICS PROFILE. During
testing, this value can change, causing test failures. Switching to
SHOWPLAN_ALL will give a plan without outputing memory usage.

Signed-off-by: Walt Boettge <[email protected]>
Signed-off-by: Rohit Bhagat <[email protected]>
Copy link
Contributor

@jsudrik jsudrik left a comment

Choose a reason for hiding this comment

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

Approved

@jsudrik jsudrik merged commit 0b610a4 into babelfish-for-postgresql:BABEL_2_7_STABLE Nov 24, 2023
23 checks passed
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.

4 participants