12230419723
77%

Ran 09 Dec 2024 07:24AM UTC

Jobs 1

Files 115

Run time 1min

Badge

Embed ▾

Committed 09 Dec 2024 06:48AM UTC coverage: 74.809%. Remained the same

Build # 12230419723

Build Type

push

github

Committed by

web-flow

Commit Message

Modify upgrade scripts to obtain correct server level collation during upgrade (#3154)

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>

Run Details

46469 of 62117 relevant lines covered (74.81%)

161063.43 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	12230419723.1	09 Dec 2024 07:24AM UTC	115	74.81	GitHub Action Run

babelfish-for-postgresql / babelfish_extensions / 12230419723
77%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 12230419723

babelfish-for-postgresql / babelfish_extensions / 12230419723 77%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 12230419723

babelfish-for-postgresql / babelfish_extensions / 12230419723
77%

README BADGES
x