Babelfish for PostgreSQL provides the capability for PostgreSQL to work with applications written for Microsoft SQL Server. Babelfish understands the SQL Server wire-protocol and T-SQL, the Microsoft SQL Server query and procedural language, so you don’t have to switch database drivers or rewrite all of your application queries.
As an effort to fix string functions, we introduced various function definitions is sys schema, but there are a few places where we overlooked to prepend PG_CATALOG in the function calls inside system view/functions which may cause mVU/MVU failures due to error while executing upgrade scripts due to invalid argument type.
Affected functions were - RTRIM, STRING_AGG, SUBSTRING, LOWER.
2. Changes made to fix the issues
Prepended appropriate namespace at suitable function calls as a proactive measure to prevent m/MVU failures, Since, invalid datatypes for sys function definitions which can cause issue will now be redirected to pg_catalog function definitions and will work correctly as before.
[x] 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.
Description
1. Issues
2. Changes made to fix the issues
Task: BABEL- 5362 Authored-by: Anikait Agrawal agraani@amazon.com Signed-off-by: Anikait Agrawal agraani@amazon.com
Test Scenarios Covered
Use case based -
Boundary conditions -
Arbitrary inputs -
Negative test cases -
Minor version upgrade tests -
Major version upgrade tests -
Performance tests -
Tooling impact -
Memory tests -
Client tests -
Check List
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.