Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix failure in MVU with non-default server collation name (#2054)
Currently, in upgrade scripts, server_collation_name is set to restored_server_collation_name in babelfishpg_common upgrade scripts only and then GUC restored_server_collation_name is being reset. Now this server_collation_name is being set only for that connection, when a new connection is created server_collation_name will contain the default value. This will cause issue when different connections are used to update babelfishpg_common and babelfishpg_tsql, as the server_collation_name contains default value in connection in which babelfishpg_tsql is getting updated, but expected value of server_collation_name is the value of restored_server_collation_name. Due to this, incorrect collation(default collation) is getting assigned to a column in spt_tablecollation_view instead of the collation stored in restored_server_collation_name. This commit will resolve this issue by setting the server_collation_name to restored_server_collation_name in babelfishpg_tsql upgrade scripts as well. Cherry-picked from 482eb2d Signed-off-by: Rohit Bhagat [email protected]
- Loading branch information