babelfish-for-postgresql
/
babelfish_extensions
/
12271682337
76%
BABEL_5_X_DEV: 77%
BABEL_5_X_DEV: 77%
|
Ran
|
Jobs
1
|
Files
115
|
Run time
1min
|
Badge
Embed ▾
README BADGES
|
coverage: 74.731%. Remained the same
push
github
web-flowModify upgrade scripts to obtain correct server level collation during upgrade (#3219) In all MVU sql scripts, we update the server collation name and reset the restored_server_collation_name GUC. During the upgrade from 16.1 --> latest (17), the upgrade started failing for non-default server collation like chinese_prc_ci_as as we did not have correct collation information and the collation of columns of views were trying to get updated. This is because, we never updated the collation related information in any of the upgrade script post 16.1, hence it was always picking the default value which is bbf_unicode_cp1_ci_as. The issue may come up in case when user is performing upgrade from some version of 15 (before 15.6) to latest if we have defines some view which contains collatable column in upgrade script and the server level collation is different than default collation. We address the issue by updating the collation related information in the necessary upgrade scripts. BABEL-5415 Signed-off-by: Shameem Ahmed <shmeeh@amazon.com> (cherry picked from commit d936b3343)
45782 of 61262 relevant lines covered (74.73%)
167095.48 hits per line
Jobs
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 12271682337.1 | 115 |
74.73 |
GitHub Action Run |
