[Bug] [UOS1050a, UOS1060e] invalid byte sequence for encoding "UTF8": 0xba when create table

[congxuebin]

Cloudberry Database version

PostgreSQL 14.4 (Cloudberry Database 1.5.5+dev.61.g3ccb452c build 78117 commit:3ccb452c) (HashData Lightning 1.5.5+dev.61.g3ccb452c build 78117 commit:3ccb452c) on x86_64-pc-linux-gnu, compiled by gcc (GCC) 10.2.1 20201112 (UOS 10.2.1-8), 64-bi
t compiled on Jun 26 2024 04:10:10
(1 row)

What happened

ICW case dispatch_encoding failed against UOS 1050a system. +ERROR: invalid byte sequence for encoding "UTF8": 0xba

set log_min_duration_statement to 0;
 create table truncate_test ("колонка 1" int, "колонка 2" int, "колонка 3" int, "колонка 4" int, "колонка 5" int,
-"колонка 6" int, "колонка 7" int, "колонка 8" int, "колонка 9" int, "колонка 10" int, "колонка 11" int,
+"колонка 6" int, "колонка 7" int, "колонка 8" int, "колонка 9" int, "колонÐ<80>ºÐ° 10" int, "колонка 11" int,
 "колонка 12" int, "колонка 13" int, "колонка 14" int, "колонка 15" int, "колонка 16" int, "колонка 17" int,
 "колонка 18" int, "колонка 19" int, "колонка 20" int, "колонка 21" int, "колонка 22" int, "колонка 23" int,
 "колонка 24" int, "колонка 25" int, "колонка 26" int, "колонка 27" int, "колонка 28" int, "колонка 29" int,
 "колонка 30" int, "колонка 31" int, "колонка 32" int, "колонка 33" int, "колонка 34" int, "колонка 35" int,
 "колонка 36" int, "колонка 37" int, "колонка 38" int, "колонка 39" int, "колонка 40" int, "оÑ<81>обаÑ<8f> колонка" int);
+ERROR:  invalid byte sequence for encoding "UTF8": 0xba
 select split_part(logmessage, 'statement: ', 2) from gp_toolkit.__gp_log_segment_ext where logmessage ilike
 '%create table truncate_test%' and logmessage not ilike '%gp_toolkit.__gp_log_segment_ext%' order by logtime desc limit 1;
-                                                    split_part                                                    
-------------------------------------------------------------------------------------------------------------------
- "колонка 12" int, "колонка 13" int, "колонка 14" int, "колонка 15" int, "колонка 16" int, "колонка 17" int,     +
- "колонка 18" int, "колонка 19" int, "колонка 20" int, "колонка 21" int, "колонка 22" int, "колонка 23" int,     +
- "колонка 24" int, "колонка 25" int, "колонка 26" int, "колонка 27" int, "колонка 28" int, "колонка 29" int,     +
- "колонка 30" int, "колонка 31" int, "колонка 32" int, "колонка 33" int, "колонка 34" int, "колонка 35" int,     +
- "колонка 36" int, "колонка 37" int, "колонка 38" int, "колонка 39" int, "колонка 40" int, "о
- "колонка 6" int, "колонка 7" int, "колонка 8" int, "колонка 9" int, "колонка 10" int, "колонка 11" int,         +
- create table truncate_test ("колонка 1" int, "колонка 2" int, "колонка 3" int, "колонка 4" int, "колонка 5" int,+
-(1 row)
+ split_part 
+------------
+(0 rows)

What you think should happen instead

set log_min_duration_statement to 0;
create table truncate_test ("колонка 1" int, "колонка 2" int, "колонка 3" int, "колонка 4" int, "колонка 5" int,
"колонка 6" int, "колонка 7" int, "колонка 8" int, "колонка 9" int, "колонка 10" int, "колонка 11" int,
"колонка 12" int, "колонка 13" int, "колонка 14" int, "колонка 15" int, "колонка 16" int, "колонка 17" int,
"колонка 18" int, "колонка 19" int, "колонка 20" int, "колонка 21" int, "колонка 22" int, "колонка 23" int,
"колонка 24" int, "колонка 25" int, "колонка 26" int, "колонка 27" int, "колонка 28" int, "колонка 29" int,
"колонка 30" int, "колонка 31" int, "колонка 32" int, "колонка 33" int, "колонка 34" int, "колонка 35" int,
"колонка 36" int, "колонка 37" int, "колонка 38" int, "колонка 39" int, "колонка 40" int, "оÑ<81>обаÑ<8f> колонка" int);
NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'колонка 1' as the Cloudberry Database data distribution key for this table.
HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
select split_part(logmessage, 'statement: ', 2) from gp_toolkit.__gp_log_segment_ext where logmessage ilike
'%create table truncate_test%' and logmessage not ilike '%gp_toolkit.__gp_log_segment_ext%' order by logtime desc limit 1;
                                                    split_part
------------------------------------------------------------------------------------------------------------------
 create table truncate_test ("колонка 1" int, "колонка 2" int, "колонка 3" int, "колонка 4" int, "колонка 5" int,+
 "колонка 6" int, "колонка 7" int, "колонка 8" int, "колонка 9" int, "колонка 10" int, "колонка 11" int,         +
 "колонка 12" int, "колонка 13" int, "колонка 14" int, "колонка 15" int, "колонка 16" int, "колонка 17" int,     +
 "колонка 18" int, "колонка 19" int, "колонка 20" int, "колонка 21" int, "колонка 22" int, "колонка 23" int,     +
 "колонка 24" int, "колонка 25" int, "колонка 26" int, "колонка 27" int, "колонка 28" int, "колонка 29" int,     +
 "колонка 30" int, "колонка 31" int, "колонка 32" int, "колонка 33" int, "колонка 34" int, "колонка 35" int,     +
 "колонка 36" int, "колонка 37" int, "колонка 38" int, "колонка 39" int, "колонка 40" int, "о
(1 row)

How to reproduce

startup huaweicloud server: 45f4b9a4-9a8c-45b3-adcb-b6f0bb6f724e
logon to 192.168.192.232.
su - gpadmin
gpstart
pushd /code/cbdb_src/src/test/regress;make installcheck-debug

Operating System

UOS1050a, UOS1060e

Anything else

No response

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct.

[congxuebin]

As we discussed, the DDL statement run succeeded via psql, but failed via pg_regress. I would look into pg_regress.