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

[valgrind] Invalid read in postquel_sub_params #270

Open
wants to merge 3 commits into
base: BABEL_3_X_DEV__PG_15_X
Choose a base branch
from

Conversation

Suthapalli-Ramya-satya-vasavi-srija

Description

Previously in postquel_sub_params there is an invalid read when ran valgrind aganist it. Fixed the invalid read in postquel_sub_params when valgrind ran aganist the fuction by passing the correct values.

Issues Resolved

BABEL-4476

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 PostgreSQL license, 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.

Previously in postquel_sub_params there is an invalid read when ran
valgrind aganist it. Fixed the invalid read in postquel_sub_params when
valgrind ran aganist the fuction by passing the correct values.

Task: BABEL-4476
Signed-off-by: vasavi suthapalli <[email protected]>
prm->value = MakeExpandedObjectReadOnly(fcinfo->args[i].value,
prm->isnull,
get_typlen(0));
prm->ptype = 0;
Copy link
Contributor

Choose a reason for hiding this comment

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

This ptype being zero doesn't seem right to me. Btw, this issue seem to be community PG issue, we should report it in the community and try to find the solution collectively.

Copy link
Contributor

Choose a reason for hiding this comment

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

agree with @Deepesh125 , @Suthapalli-Ramya-satya-vasavi-srija is there a way we can fix this on the extension? If not, then we may need to report it in the community.

@Deepesh125 more info in the Jira.

Copy link
Contributor

Choose a reason for hiding this comment

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

if this is an issue in engine code, we should not fix it in extension.

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