add bbf namespace ext to syscache #224
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Today, many helper routines such as
get_logical_schema_name,get_dbid_from_physical_schema_name,has_ext_info,del_ns_ext_infoperform heap scans onbabelfish_namespace_ext, which can lead to slow performance. These routines are called internally for various utility operations like creating a database or using a database. As the size of thebabelfish_namespace_extcatalog keeps increasing (as observed in BABEL-3869), the performance of these operations degrades.This PR includes changes that
Add a key name in
SysCacheIdentifierenum for bbf_namespace_ext catalog, that will be used to search in syscache.Extension PR - babelfish-for-postgresql/babelfish_extensions#1875
Issues Resolved
BABEL-4414
Signed-off-by: Sandeep Kumawat [email protected]
Check List
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.