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

release sys cache reference after string literal hook #254

Conversation

tanscorpio7
Copy link
Contributor

@tanscorpio7 tanscorpio7 commented Nov 10, 2023

Description

Release syscache reference when returning not null nodes from string literal hook to avoid cache reference leak

Engine PR: #254

Extension PR: babelfish-for-postgresql/babelfish_extensions#2009

Issues Resolved

[BABEL-1940]

Sign-off

Signed-off-by: Tanzeel Khan [email protected]
Co-authored-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 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.

…sh-for-postgresql#248)

Release syscache reference when returning not null nodes from string literal hook to avoid cache reference leak

Engine PR: babelfish-for-postgresql#248
Extension PR: babelfish-for-postgresql/babelfish_extensions#1957

Task: 1940
Signed-off-by: Tanzeel Khan <[email protected]>
@Deepesh125 Deepesh125 merged commit 474e445 into babelfish-for-postgresql:BABEL_2_X_DEV__PG_14_X Nov 10, 2023
1 check passed
Deepesh125 pushed a commit to babelfish-for-postgresql/babelfish_extensions that referenced this pull request Nov 10, 2023
Binary data type simply stores hex codes but when transformed to and from varchar, use of correct encoding becomes important. For example the symbol '™' is stored as
0xE284A2 in UTF-8 enc. while
0x99 in Win encoding
From users perspective they must see the hex value which is congruent to their server encoding.

To fix this we do necessary encoding to source data in varchar <--> varbinary internal functions.
Length checks should be done when data (hex string) is in server encoding.

We must also handle the case for string literal to binary types. So we explicitly call the varcharvarbinary conversion when a string literal is being casted to binary data type.

Also added CAST functions for sys.BBF_VARBINARY to sys.BBF_BINARY and vice versa
these cast are being used in geography and geometry cast functions
made necessary changes to geography and geometry casts as well
i.e. CAST (CAST ($1 AS sys.VARCHAR) AS sys.bbf_varbinary) --> CAST ($1 AS sys.bbf_varbinary)

Engine PR: babelfish-for-postgresql/postgresql_modified_for_babelfish#254
Extension PR: #2009

Task: BABEL-1940
Signed-off-by: Tanzeel Khan <[email protected]>
Co-authored-by: Rohit Bhagat <[email protected]>
@tanscorpio7 tanscorpio7 deleted the BABEL_1940_2_X branch February 7, 2024 09:19
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.

2 participants