【标题描述】:修改standard_conforming_strings参数为off后，切换到刚刚创建的新库会出现core
【测试类型：SQL功能
【测试版本：6.0.0】
问题描述 在修改standard_conforming_strings参数为off后，创建一个新库，切换到刚刚创建的新库会出现core
【测试环境】(单机/1主x备x级联备):
单机
【被测功能】:
standard_conforming_strings 开关
【测试类型】:
功能测试
【数据库版本】(查询命令: gaussdb -V):
6.0.0
【预置条件】:
standard_conforming_strings 设置为off
【操作步骤】(请填写详细的操作步骤):

1. standard_conforming_strings 设置为off
2. 创建一个新库
3. 连接到新库
   【预期输出】:
   正常连接到新库，可以正常执行作业
   【实际输出】:
   输出core，连接失败
   【原因分析】:
4. 这个问题的根因
   关闭了standard_conforming_strings 开关之后会把''当成转义符，所以会出现跑飞。

【日志信息】(请附上日志文件、截图、coredump信息):
#1sys_waitpid (pid=pid@entry=2660965，status=status@entry=0xffd299db759c,options=options@entry=1073741824) at bbox_
#20x0000aaad41c0bf88 inBBOX_GetClonePidResu1t(iC1onePid=iC1onePid@entry=2660965,pstArgs=pstArgs@entry=0xffd299db7
at bbox_threads.cpp:572
#30x0000aaad41c0c2ec inBBOX_GetA11Threads (enType=GET_TYPE_DUMP，pDone=pDone@entry=0xaaad41c02d58<BBOX_FinishDumpF
pDoneArgs=0xffffff80ffffffe0,pDoneArgs@entry=0xffd299db7778，pCa1lback=) at bbox_threads.cpp:700
#40x0000aaad41c02f9c inBBOX_CreateCoredump(file_name=0xffd299db7888"/database/gbase/corefi1e//core-gaussdb-2659726
file_name@entry=0x0) at bbox_create. cpp:440
#50x0000aaad41c0d9b8 in bbox_handler (sig=, si=, uc=) at gs_bbox.cpp:112
#6
#70x0000aaad415b9af4 in function parse error_transpose
#80x0000aaad4267695c in plpgsql_compile_error_callback(arg=) at pl_package.cpp:1229
(prosrc=0xaaad4808c000<g_tagStrArr+5504>"\v\003") at pg_proc
#90x0000aaad419ccf6c in errfinish (dummy=dummy@entry=0) at elog. cpp:543
#10 0x0000aaad41706340 in check_escape_warning (yyscanner=yyscanner@entry=0xffd3351fa080) at scan.1:1827
#11 0x0000aaad41740alc in check_string_escape_warning (yyscanner=0xffd3351fa080,Tychar=) at scan.1:1820
#12core_yylex (yy1val_param=yylval_param@entry=0xffd299db9298，yy11oc_param=yy11oc_param@entry=0xffd299db92c8,yyscanne
#130x0000aaad42698fec in internal_yylex (auxdata=auxdata@entry=0xffd299db9298) at p1_scanner.cpp:387
#14 0x0000aaad426995f0 in plpgsql_parse_cursor_attribute (1oc=0xffd299db9414,1oc@entry=0xffd299db9464) at pl_scanner.cp
#15 0x0000aaad42699da0 in plpgsql_yylex() at p1_scanner.cpp:132
#16 0x0000aaad426b3ce0 in read_sql_construct6(until=unti1@entry=443,unti12=65490，unti12@entry=0,unti13=-1713661276,
unti15=43693，unti15@entry=0,unti16=-1,unti16@entry=0, expected=0xffffffffffffffff <Address 0xffffffffffffffff out
expected@entry=0xaaad46e019a8 “THEN"，sqlstart=0xffd299dfa3e8 “M"，sqlstart@entry=0xaaad44162a40“SELECT ",isexpress
va1id_sq1=va1id_sq1@entry=true,trim=trim@entry=true,start1oc=start1oc@entry=0x0,endtoken=, endtoker
tokenstack=tokenstack@entry=0x0,issaveexpr=,issaveexpr@entry=false) at gramy:8639
#17 0x0000aaad426b630c in read sql_construct (endtoken=0x0,startloc=0x0, trim=true, valid_sql=true, isexpression=true,s
expected=expected@entry=0xaaad46e019a8 “THEN"， unti13=0, unti12=0,until=unti1@entry=443)at gramy:8913
#18 read_sq1_expression(until=until@entry=443,expected=expected@entry=0xaaad46e019a8“THEN") at gram.y:7925
#19 0x0000aaad426bd8d0 in plpgsq1_yyparse() at gram y:5830
#20 0x0000aaad426719b4 in do_compile (fcinfo=fcinfo@entry=0x516ac4a6a1e60a1d, proc_tup=proc_tup@entry=0xffd299dbc8e0,func
func@entry=0x516a91d97a5af9d1,hashkey=0xffd299dcc8e0,hashkey@entry=0xffd299dbc968, for validator=fn