- Community - mailweb.opengauss.org

openGauss社区PR和Issue自动分配SIG组以及维护者功能上线
by Xiangxinyong (Edison) 31 Aug '22

31 Aug '22

各位openGauss社区的开发者，大家好， openGauss社区PR和Issue自动分配SIG组以及维护者功能已经上线，感谢来自SIG Infra团队的@曹志和@汪豪这一个月以来的辛勤工作。 openGauss社区里面现在提交的PR和Issue几乎都打上了SIG组的标签，同时在PR和Issue下面有一行机器人打上的PR和Issue检视的第一责任人标签以及对应的Maintainer和Committer。这样方便提交PR和Issue的开发者可以轻松找到社区各个SIG组的负责人进行检视，下面有一个SIG SQLEngine的PR提示信息供参考： https://gitee.com/opengauss/openGauss-server/pulls/2110 [cid:image003.jpg@01D8BD57.364BEEA0] 同时由于openGauss-Server存在多个SIG组的情况，机器人无法识别一个Issue属于哪个SIG组，还请提交Issue的开发者根据如下的提示信息给openGauss-Server仓库的Issue加上SIG组标签方便SIG组的负责人进行回复。下面有这个Issue供参考： https://gitee.com/opengauss/openGauss-server/issues/I5OMGZ?from=project-iss… [cid:image006.jpg@01D8BD57.364BEEA0] 各位开发者和维护者也可以根据如下的命令给PR和Issue打上正确的标签，也请各位社区维护者及时检视自己看护的SIG组的PR，回复自己看护SIG组的Issue。序号 SIG组 SIG组标签 SIG组标签命令 1 AI sig/ai /sig ai 2 Blockchain sig/blockchain /sig blockchain 3 Certification sig/certification /sig certification 4 CloudNative sig/cloudnative /sig cloudnative 5 CM sig/cm /sig cm 6 Connectors sig/connectors /sig connectors 7 DCF sig/dcf /sig dcf 8 Docs sig/docs /sig docs 9 GIS sig/gis /sig gis 10 Graph sig/graph /sig graph 11 Infra sig/infra /sig infra 12 In-place Update sig/in-placeupdate /sig in-placeupdate 13 IoT sig/iot /sig iot 14 KnowledgeGraph sig/knowledgegraph /sig knowledgegraph 15 OM sig/om /sig om 16 OPS sig/ops /sig ops 17 Plugin sig/plugin /sig plugin 18 QA sig/qa /sig qa 19 ReleaseManagement sig/rm /sig rm 20 Security sig/security /sig security 21 SecurityTechnology sig/securitytech /sig securitytech 22 SQLEngine sig/sqlengine /sig sqlengine 23 StorageEngine sig/storageengine /sig storageengine 24 Tools sig/tools /sig tools Best Regards, Edison Xiang

1 0

array_to_string结果与PG不同问题回复
by ganyang (A) 29 Aug '22

29 Aug '22

@xiyelan 您好，针对问题单https://gitee.com/opengauss/openGauss-server/issues/I5K1YY?from=pro… openGauss默认数据库为A类型，此类型下''意义为NULL，而此函数为strict函数，即输入参数有null直接返回null，创建一个PG类型或B类型的数据库可以实现与PG一样的效果。 [输入图片说明] 如果没有收到您其他的疑问的话我们将在本周关闭此问题单。

1 0

array_to_string结果与PG不同问题回复
by ganyang (A) 27 Aug '22

27 Aug '22

@xiyelan 您好，针对问题单https://gitee.com/opengauss/openGauss-server/issues/I5K1YY?from=pro… openGauss默认数据库为A类型，此类型下''意义为NULL，而此函数为strict函数，即输入参数有null直接返回null，创建一个PG类型或B类型的数据库可以实现与PG一样的效果。 [输入图片说明] 如果没有收到您其他的疑问的话我们将在下周关闭此问题单。

1 0

help ,怎么设置openGauss全局不区分大小写
by 15515509121＠163.com 26 Aug '22

26 Aug '22

help ,怎么设置openGauss全局不区分大小写？ 15515509121(a)163.com

2 1

华为云 ecs kylin v10安装 openGauss报错
by ♚ 她的笑 24 Aug '22

24 Aug '22

您好      目前系统安装openGauss的过程报错，这次是报网卡错误。截图如下可以确认pyhon 没有问题  是 python3 如上执行命令对应的报错文件中的错误如下截图，辛苦看下如何解决，感谢。

1 0

openGauss社区邀您参加8月25日云和恩墨大讲堂 x openGauss Meetup x 鲲鹏生态孵化营【成都站】
by Xiangxinyong (Edison) 23 Aug '22

23 Aug '22

活动主题：把企业级的数据库能力带给用户，共筑计算新生态共赢数字新时代活动时间： 2022年8月25日（周四）13:30-18:00 活动地点：成都市高新区泰和二街66号新兰天地酒店3楼新兰厅主办单位：云和恩墨、openGauss社区、四川鲲鹏创新中心、成都鲲鹏计算产业联盟联合宣传：墨天轮、Gauss松鼠会、虚谷伟业报名参会： https://jinshuju.net/f/gb9XGg 防疫须知： 1、因为疫情防控需要，参会人员凭绿码入场，并请全程佩戴口罩。 2、请参会者确保14天之内未到过疫情中高风险地区或接触过疫情中高风险地区人员。 3、其他问题，请联系微信openGauss小助手: openGauss-bot。 Best Regards, openGauss社区

1 0

opengauss：fail to allocate a zone
by 微唯。薇 04 Aug '22

04 Aug '22

一主一备模式下，进行简单测试，一段时间后显示：fail to allocate a zone 通过提供的工具收集日志，结果是死锁导致的： 2022-08-03 14:14:59.865 62ea1252.5025 postgres 139780237289216 PostgreSQL JDBC Driver 1538516 dn_6001_6002 40P01 3377699720531497 [BACKEND] ERROR: deadlock detected 2022-08-03 14:14:59.865 62ea1252.5025 postgres 139780237289216 PostgreSQL JDBC Driver 1538516 dn_6001_6002 40P01 3377699720531497 [BACKEND] DETAIL: Process 139780237289216 waits for ShareLock on transaction 1538556; blocked by process 139780876728064. Process 139780876728064 waits for AccessExclusiveLock on tuple (19808,36) of (relation 16390, bucket 0) of database 15484; blocked by process 139779890865920. Process 139779890865920 waits for ShareLock on transaction 1538516; blocked by process 139780237289216. Process 139780237289216: delete from users where user_name = $1 线程代码： public class DelectTest extends Thread { String sql = "delete from users where user_name = ?;" + "delete from users where user_name = ?;" + "delete from users where user_name = ?"; JDBCUtil jdbc = new JDBCUtil(); public void run(){ Long startTime = System.currentTimeMillis(); Long endTime = null; boolean flag = true; while(flag){ try { DelectTest.sleep(800); PreparedStatement statement = jdbc.getStatement(sql); statement.setString(1,"zhangsan"); statement.setString(2,"zhaoliu"); statement.setString(3,"longqi"); int i = statement.executeUpdate(); System.out.println("成功地删除了"+ i +"条数据"); //MyLogger.info("成功地删除了"+ i +"条数据"); endTime = System.currentTimeMillis(); if(endTime - startTime > 86400000*3){ flag = false; } } catch (SQLException throwables) { throwables.printStackTrace(); //MyLogger.warning(throwables.getMessage()); } catch (InterruptedException e) { e.printStackTrace(); } finally { jdbc.closeSource(); } } } } 之后将测试关闭程序，只要对数据库进行写操作，就会显示fail to allocate a zone，需要重启数据库才能恢复。请问这是为什么呢？怎么解决

2 1

by 微唯。薇 04 Aug '22

04 Aug '22

help

1 0

Re: confirm 24ba83f9ff17d5900f5898b9469407fa533b37b8
by ct0986 02 Aug '22

02 Aug '22

注册opengauss社区账号 On 8/2/2022 15:35，<community-confirm+24ba83f9ff17d5900f5898b9469407fa533b37b8(a)opengauss.org> wrote：邮箱订阅确认您好，这是opengauss.org的邮件列表服务。我们收到来自以下邮箱的注册请求： ct0986(a)126.com 在开始使用本站的邮件列表服务之前，请确认这是您的邮箱。你可以通过回复此消息来进行确认，请保持回信的主题不变。若您不想注册该邮箱，请忽略此消息。若您怀疑自己被恶意订阅了该列表或有其他任何疑问，请联系： community-owner(a)opengauss.org Email Address Registration Confirmation Hello, this is the GNU Mailman server at opengauss.org. We have received a registration request for the email address ct0986(a)126.com Before you can start using GNU Mailman at this site, you must first confirm that this is your email address. You can do this by replying to this message, keeping the Subject header intact. If you do not wish to register this email address, simply disregard this message. If you think you are being maliciously subscribed to the list, or have any other questions, you may contact community-owner(a)opengauss.org

1 0

opengauss 3.0.1
by qinhao＠newland.com.cn 21 Jul '22

21 Jul '22

Hi 看到 opengauss 3.0.0 升级到了 3.0.1，请问什么情况下会升级小版本？新大陆软件秦浩 mobile: 17625988619 e-mail:qinhao@newland.com.cn

2 2

OpanGauss中内置函数的插入机制
by 游奕桁 16 Jul '22

16 Jul '22

Hi 近期在开发的过程中需要插入新的内置函数，但是发现opengauss中内置函数的插入机制与postgresql中不同，经过了多种尝试都以失败告终，想请问一下opengauss中的内置函数是通过什么样的机制插入到数据库中的，以及源码中后缀名为.h_for_llt文件是如何发挥作用的，在现有的源码讲解博客中没有发现详细的相关内容。望回复

1 0

chunk pool exceeded high red mark 34075
by qinhao＠newland.com.cn 15 Jul '22

15 Jul '22

Hi, I was trying to run TPC-E test on OpenGauss MOT tables, however, when loading data into MOT tables for about half an hour, the gaussdb process exit with following messages in log: 2022-07-05 14:40:11.012 [MOT] <TID:2990935/00023> <SID:00154/00023> [WARNING] <Memory> Global[0] chunk pool exceeded high red mark 34075, and is now defined to be in emergency state What does that mean? 新大陆软件秦浩 mobile: 17625988619 e-mail:qinhao@newland.com.cn

2 2

openGauss 2周年专属你的纪念海报
by opengauss 13 Jul '22

13 Jul '22

openGauss开发者您好，      感谢2年来的支持，请查收openGauss 开源2周年专属你的纪念海报。          openGauss社区

1 0

openGauss社区诚邀您参加openGauss Developer Day 2022
by opengauss 23 Jun '22

23 Jun '22

openGauss社区开发者们大家好， openGauss Developer Day 2022是openGauss社区发起面向数据库开发者的年度技术盛会。感谢大家一直以来对openGauss的支持，openGauss社区开源2年来，在技术、生态、商业和社区治理等方面发展显著。为践行openGauss社区共建、共享、共治的理念，打造中国最具创新力的开源数据库根社区，现诚邀学术专家，行业用户，合作伙伴，开发者共同探讨数据库面向多场景的技术创新，分享基于openGauss的行业联合创新成果及商业实践，献计社区治理完善，讨论社区版本规划。活动时间：2022年7月14-15日活动地点：北京昆泰嘉瑞文化中心 openGauss社区首届开发者大会openGauss Developer Day 2022的演讲征集、赞助征集、SIG征集通道现已开放，欢迎提交参与。 Call for Speaker（演讲征集）: https://shimo.im/forms/loqeWr2z40Fw4NAn/fill （分享技术 or 实践，出色的speaker需要你出现） Call for Sponsor（赞助征集）: https://shimo.im/forms/RKAWVlw7YYu5YGk8/fill （主办or协办，分论坛你说了算） Call for SIG（SIG征集）: https://shimo.im/forms/vVqRV1woxPheEBqy/fill （兴趣和技术，合在一起就是酷）   报名15日线下会议通道：https://e-campaign.huawei.com/m/aIFru2 Best Regards, openGauss社区理事会  

1 0

openGauss社区诚邀您参加openGauss Developer Day 2022
by opengauss 23 Jun '22

23 Jun '22

openGauss社区开发者们大家好， openGauss Developer Day 2022是openGauss社区发起面向数据库开发者的年度技术盛会。感谢大家一直以来对openGauss的支持，openGauss社区开源2年来，在技术、生态、商业和社区治理等方面发展显著。为践行openGauss社区共建、共享、共治的理念，打造中国最具创新力的开源数据库根社区，现诚邀学术专家，行业用户，合作伙伴，开发者共同探讨数据库面向多场景的技术创新，分享基于openGauss的行业联合创新成果及商业实践，献计社区治理完善，讨论社区版本规划。   活动时间：2022年7月14-15日活动地点：北京昆泰嘉瑞文化中心   openGauss社区首届开发者大会openGauss Developer Day 2022的演讲征集、赞助征集、SIG征集通道现已开放，欢迎提交参与。   Call for Speaker（演讲征集）: https://shimo.im/forms/loqeWr2z40Fw4NAn/fill （分享技术 or 实践，出色的speaker需要你出现）   Call for Sponsor（赞助征集）: https://shimo.im/forms/RKAWVlw7YYu5YGk8/fill （主办or协办，分论坛你说了算）   Call for SIG（SIG征集）: https://shimo.im/forms/vVqRV1woxPheEBqy/fill （兴趣和技术，合在一起就是酷）   报名15日线下会议通道：https://e-campaign.huawei.com/m/aIFru2     Best Regards, openGauss社区理事会  

1 0

OpenGauss没有实现pCALC吗？（OpenGauss does not implement pCALC？）
by qinhao＠newland.com.cn 22 Jun '22

22 Jun '22

Hi 最近在对比CALC的论文研究MOT检查点代码，发现capture阶段向磁盘写数据的代码，好像没有实现CALC论文中所讲的pCALC，每次做checkpoint，将MOT表所有记录都写到磁盘文件（CheckpointWorkerPool::WriteTableDataFile）中，而不是只保存修改了的记录，我找不到实现pCALC的代码，这样做checkpoint是不是代价太大了？而且我在代码中发现"MOT does not support incremental checkpoint"，这是不是说目前不支持CALC中的pCALC？如果我的理解有问题，请纠正。 Recently, I was studying the MOT checkpoint code comparing with CALC paper, and found no implemention of pCALC, which means, in the capture phase, all MOT records are written to the disk(CheckpointWorkerPool::WriteTableDataFile), not just updated records. Is it too expensive to save all records of MOT tables? And I found some messages in code like "MOT does not support incremental checkpoint", does that mean pCALC is not supported in OpenGauss currently？Please correct me, if my understanding is wrong. 新大陆软件秦浩 mobile: 17625988619 e-mail:qinhao@newland.com.cn

2 2

多事务并发调用CSNManager::GetNextCSN()，导致争用
by qinhao＠newland.com.cn 22 Jun '22

22 Jun '22

Hi, 各位大佬，又来麻烦大家了，最近在看MOT事务协议的代码，再次感谢一下Vinoth关于CSN的指点，对比silo论文，发现OpenGauss在通过有效性确认后，调用CSNManager::GetNextCSN()生成全局唯一CSN，然而这个实现，并发事务线程都会尝试原子性地对CSNManager::m_csn加1，它是个所有事务共享的变量，这不就带来（事务线程间的）争用（contention）了吗？ OpenGauss的代码，好像并没有采用silo的设计 ――通过Epoch，各事务独立生成TID，以避免争用？或者是这种争用微不足道？谢谢新大陆软件秦浩 mobile: 17625988619 e-mail:qinhao@newland.com.cn

2 2

openGauss社区邀您参加6月15日兰州Meetup
by Xiangxinyong (Edison) 10 Jun '22

10 Jun '22

活动背景： openGauss社区用开源的魅力吸引真正热爱技术并持续探索的用户和开发者，Meetup通过打造一个自由、活跃的前沿技术交流空间，定期邀请业内专家分享与深度探讨数据库领域的前瞻性技术思考与经验，共同构建一个能够融合多元化技术架构的企业级开源数据库社区。活动主题：打造最具创新力开源数据库社区把企业级的数据库能力带给用户活动时间： 2022年6月15日（周三）14:00-17:20 活动地点：兰州市七里河区彭园路创智国际甘肃鲲鹏生态创新中心活动主办方：兰州高新技术产业开发区管理委员会、兰州市工业和信息化局、openGauss社区活动承办方：甘肃鲲鹏生态创新中心、海量数据、甘肃九霄鲲鹏科技有限公司报名参会： https://www.slidestalk.com/m/916 防疫须知： 1、因为疫情防控需要，参会人员凭绿码入场，并请全程佩戴口罩。 2、请参会者确保14天之内未到过疫情中高风险地区或接触过疫情中高风险地区人员。 3、其他问题，请联系微信openGauss小助手:openGauss-bot。 Best Regards, openGauss社区

1 0

疑问：MOT中的Epoch
by qinhao＠newland.com.cn 10 Jun '22

10 Jun '22

Hi, 最近在看silo论文，尝试理解MOT的代码，不过发现MOT中好像没有silo中关于Epoch的逻辑？是MOT没有使用Epoch吗？使用silo的事务提交算法，可以不使用Epoch吗？我对silo和MOT代码的理解还不够，谁能指点解释一下，谢谢！新大陆软件秦浩 mobile: 17625988619 e-mail:qinhao@newland.com.cn

2 2

关于社区PR提交与审查的疑问
by 陈泽 10 Jun '22

10 Jun '22

Hi all，目前openGauss社区开放了很多SIG组及相关会议来讨论一些feature的开发合入问题。但是对于一些偶然发现的小的bug，是否需要先参加相关的SIG会议提交议题然后再提交PR呢？同时，现在og仓库中存在很多开启的PR很长时间没有任何动态，似乎是还没有进行审查，我看社区的介绍是只有Committer有权限审查代码，关于这点我们是否可以借鉴pg社区，允许更多的人添加自己为审查人员对PR进行审查，由至少一个committer确认即可，可以大幅降低committer的工作量，提高PR的合入效率。甚至也可以再开一个reviewer的统计页面，提高社区人员参与PR审查工作的积极性。陈泽数据库内核研发工程师云和恩墨联系我  

1 0

openGauss向量化引擎执行排序时内存统计的一个问题
by 闫宗帅 31 May '22

31 May '22

你好，在学习opengauss向量化引擎过程中，有一个疑惑，是不是遇到了bug？ openGauss向量化引擎在排序过程种，需要通过UseMem函数统计其内存使用。比如在Batchsortstate：：InitCommon函数中：第732行m_storeColumns.Init会申请对m_storeColumns.m_memValues申请10240* sizeof(MultiColumns));但是在第735行统计使用内存的时候，从m_storeColumns开始了，应该是从m_storeColumns.m_memValues这里开始才准确吧。这两个地址获取的GetMemoryChunkSpace大小明显不一样，通过修改代码分别获取下图中大小：得到的结果分别为： work_mem最小是64KB，在此情况下，光在第732行处就用掉了245816B，大概240KB，超过了64KB，应该LackMem报错的。但如果是代码中流程化，仅标记用了1064B。第735行是否应该修改为：UseMem(GetMemoryChunkSpace(m_storeColumn.m_memValues))

1 0

关于展示openGauss社区核心代码仓库贡献总和的讨论
by Xiangxinyong (Edison) 30 May '22

30 May '22

Hi team，在下午的SIG Infra例会上，我们讨论了社区贡献看板：https://datastat.opengauss.org/zh/detail的单位成员贡献展示。当前openGauss社区有61个仓库：https://gitee.com/opengauss 后续考虑通过添加一个下拉框，用于展示在每个仓库的单位成员贡献。例会上讨论是否选出几个社区的核心代码仓库，在展示单个仓库贡献的同时，展示几个核心代码仓库的单位成员贡献总和。欢迎大家发表对展示几个核心代码仓库总和的看法？如果展示，我们选择哪些仓库作为核心代码仓库？ Best Regards, Edison Xiang

1 0

回复郭炜亮
by 小徍 25 May '22

25 May '22

测试的功能是在线迁移还是离线迁移在线迁移的话检查一下进程是否正常建议把完整的迁移命令也发过来，方便定位问题可参照以下资料： https://opengauss.org/zh/blogs/blogs.html?post/totaj/%E5%A6%82%E4%BD%95%E4%…

1 0

使用chameleon3.0 将MySQL迁移至openGauss不生效
by 郭炜亮 23 May '22

23 May '22

我使用chameleon将MySQL迁移至openGauss，日志没报错，但openGauss一直没有数据环境：CentOS7.6虚拟机，openGauss3.0，MySQL5.7，Chameleon_3.0.0 其中openGauss和MySQL装在同一台虚拟机中，迁移时使用的也是同一台虚拟机。 chameleon配置文件和迁移日志如下： -----default.yml文件内容如下：--------- --- # global settings pid_dir: '~/.pg_chameleon/pid/' log_dir: '~/.pg_chameleon/logs/' log_dest: file log_level: debug log_days_keep: 10 rollbar_key: '' rollbar_env: '' # type_override allows the user to override the default type conversion # into a different one. type_override:   "tinyint(1)":     override_to: boolean     override_tables:       - "*" # postgres  destination connection pg_conn:   host: "127.0.0.1"   port: "5432"   user: "opengauss_test"   password: "gauss_123"   database: "opengauss_database"   charset: "utf8" sources:   mysql:     readers: 4     writers: 4     db_conn:       host: "127.0.0.1"       port: "3306"       user: "mysql57_user"       password: "FireLight@Gwl99"       charset: 'utf8'       connect_timeout: 10000     schema_mappings:       db_mysql57_test: sch_mysql57_test     limit_tables:     skip_tables:     grant_select_to:     lock_timeout: "120s"     my_server_id: 100     replica_batch_size: 10000     replay_max_rows: 10000     batch_retention: '1 day'     copy_max_memory: "300M"     copy_mode: 'file'     out_dir: /tmp     sleep_loop: 1     on_error_replay: continue     on_error_read: continue     auto_maintenance: "disabled"     gtid_enable: false     type: mysql     keep_existing_schema: No     migrate_default_value: No -------default.yml文件内容结束------- ====================================================== -----------default_mysql.log 日志文件内容如下：----------- 2022-05-23 12:12:13 MainProcess INFO: Trying to add a new source 2022-05-23 12:12:13 MainProcess DEBUG: Checking if the source mysql already exists 2022-05-23 12:12:13 MainProcess WARNING: The source mysql already exists 2022-05-23 12:12:20 MainProcess INFO: Initialising the replica for source mysql 2022-05-23 12:12:20 MainProcess DEBUG: starting init replica for source mysql 2022-05-23 12:12:20 MainProcess DEBUG: There is already a database connection active. 2022-05-23 12:12:20 MainProcess DEBUG: Collecting schema mappings for source mysql 2022-05-23 12:12:20 MainProcess DEBUG: mysql version 5007038 2022-05-23 12:12:20 MainProcess INFO: deleting all the table references from the replica catalog for source mysql  2022-05-23 12:12:20 MainProcess DEBUG: Creating the loading schema _sch_linux_database_tmp. 2022-05-23 12:12:20 MainProcess DEBUG: Creating the destination schema sch_linux_database. 2022-05-23 12:12:20 MainProcess INFO: Swapping schema sch_linux_database with _sch_linux_database_tmp 2022-05-23 12:12:20 MainProcess DEBUG: Renaming schema sch_linux_database in _rename_sch_linux_database 2022-05-23 12:12:20 MainProcess DEBUG: Renaming schema _sch_linux_database_tmp in sch_linux_database 2022-05-23 12:12:20 MainProcess DEBUG: Renaming schema _rename_sch_linux_database in _sch_linux_database_tmp 2022-05-23 12:12:20 MainProcess DEBUG: Commit the swap transaction 2022-05-23 12:12:20 MainProcess DEBUG: Dropping the schema _sch_linux_database_tmp. 2022-05-23 12:12:20 MainProcess DEBUG: Changing the lock timeout for the session to 120s. 2022-05-23 12:12:20 MainProcess DEBUG: New log table : t_log_replica_mysql_1  2022-05-23 12:12:20 MainProcess INFO: Saved master data for source: mysql 2022-05-23 12:12:20 MainProcess DEBUG: Binlog file: mysql-bin.000001 2022-05-23 12:12:20 MainProcess DEBUG: Binlog position:1199 2022-05-23 12:12:20 MainProcess DEBUG: Last event: None 2022-05-23 12:12:20 MainProcess DEBUG: Next log table name: t_log_replica_mysql_1 2022-05-23 12:12:20 MainProcess DEBUG: Next batch id: 2 2022-05-23 12:12:20 MainProcess INFO: Set high watermark for source: mysql 2022-05-23 12:12:20 MainProcess INFO: init replica for source mysql is complete 2022-05-23 12:16:52 MainProcess DEBUG: There is already a database connection active. 2022-05-23 12:16:52 MainProcess DEBUG: Collecting schema mappings for source mysql 2022-05-23 12:16:52 MainProcess INFO: retrieving foreign keys metadata for schemas 'db_mysql57_test' 2022-05-23 12:16:52 MainProcess DEBUG: There is already a database connection active. 2022-05-23 12:16:52 MainProcess DEBUG: Collecting schema mappings for source mysql 2022-05-23 12:16:52 MainProcess DEBUG: Deleting the source mysql  2022-05-23 12:16:52 MainProcess DEBUG: There is already a database connection active. 2022-05-23 12:17:32 MainProcess INFO: Trying to add a new source 2022-05-23 12:17:32 MainProcess DEBUG: Checking if the source mysql already exists 2022-05-23 12:17:32 MainProcess DEBUG: Adding source mysql  2022-05-23 12:17:40 MainProcess INFO: Initialising the replica for source mysql 2022-05-23 12:17:40 MainProcess DEBUG: starting init replica for source mysql 2022-05-23 12:17:40 MainProcess DEBUG: There is already a database connection active. 2022-05-23 12:17:40 MainProcess DEBUG: Collecting schema mappings for source mysql 2022-05-23 12:17:40 MainProcess DEBUG: mysql version 5007038 2022-05-23 12:17:40 MainProcess INFO: deleting all the table references from the replica catalog for source mysql  2022-05-23 12:17:40 MainProcess DEBUG: Creating the loading schema _sch_mysql57_test_tmp. 2022-05-23 12:17:40 MainProcess DEBUG: Creating the destination schema sch_mysql57_test. 2022-05-23 12:17:41 reader-1 INFO: Copying the source table tb_customer into _sch_mysql57_test_tmp.tb_customer 2022-05-23 12:17:41 reader-1 DEBUG: estimating rows in db_mysql57_test.tb_customer 2022-05-23 12:17:41 reader-1 DEBUG: The table db_mysql57_test.tb_customer will be copied in 1  estimated slice(s) of 256 rows, using a transaction True 2022-05-23 12:17:41 reader-1 DEBUG: locking the table `db_mysql57_test`.`tb_customer` 2022-05-23 12:17:41 reader-1 DEBUG: collecting the master's coordinates for table `db_mysql57_test`.`tb_customer` 2022-05-23 12:17:41 reader-1 DEBUG: Executing query for table db_mysql57_test.tb_customer 2022-05-23 12:17:41 reader-1 DEBUG: set isolation level 2022-05-23 12:17:41 reader-1 DEBUG: beginning transaction 2022-05-23 12:17:41 reader-1 DEBUG: unlocking the tables 2022-05-23 12:17:41 reader-1 DEBUG: rolling back 2022-05-23 12:17:41 writer-3 DEBUG: Building DDL for index PRIMARY 2022-05-23 12:17:41 writer-3 INFO: Building index pk_tb_customer_1653279461_0 on _sch_mysql57_test_tmp.tb_customer 2022-05-23 12:17:41 writer-1 DEBUG: Table db_mysql57_test.tb_customer copied 1 slice of 1 2022-05-23 12:17:41 MainProcess INFO: Swapping schema sch_mysql57_test with _sch_mysql57_test_tmp 2022-05-23 12:17:41 MainProcess DEBUG: Renaming schema sch_mysql57_test in _rename_sch_mysql57_test 2022-05-23 12:17:41 MainProcess DEBUG: Renaming schema _sch_mysql57_test_tmp in sch_mysql57_test 2022-05-23 12:17:41 MainProcess DEBUG: Renaming schema _rename_sch_mysql57_test in _sch_mysql57_test_tmp 2022-05-23 12:17:41 MainProcess DEBUG: Commit the swap transaction 2022-05-23 12:17:41 MainProcess DEBUG: Dropping the schema _sch_mysql57_test_tmp. 2022-05-23 12:17:41 MainProcess DEBUG: Changing the lock timeout for the session to 120s. 2022-05-23 12:17:41 MainProcess DEBUG: New log table : t_log_replica_mysql_2  2022-05-23 12:17:41 MainProcess INFO: Saved master data for source: mysql 2022-05-23 12:17:41 MainProcess DEBUG: Binlog file: mysql-bin.000001 2022-05-23 12:17:41 MainProcess DEBUG: Binlog position:1199 2022-05-23 12:17:41 MainProcess DEBUG: Last event: None 2022-05-23 12:17:41 MainProcess DEBUG: Next log table name: t_log_replica_mysql_2 2022-05-23 12:17:41 MainProcess DEBUG: Next batch id: 1 2022-05-23 12:17:41 MainProcess INFO: Set high watermark for source: mysql 2022-05-23 12:17:41 MainProcess INFO: init replica for source mysql is complete 2022-05-23 14:27:45 MainProcess DEBUG: There is already a database connection active. 2022-05-23 14:27:45 MainProcess DEBUG: Collecting schema mappings for source mysql 2022-05-23 14:27:45 MainProcess INFO: retrieving foreign keys metadata for schemas 'db_mysql57_test' 2022-05-23 14:27:45 MainProcess DEBUG: There is already a database connection active. 2022-05-23 14:27:45 MainProcess DEBUG: Collecting schema mappings for source mysql 2022-05-23 14:27:45 MainProcess DEBUG: Deleting the source mysql  2022-05-23 14:27:45 MainProcess DEBUG: There is already a database connection active. 2022-05-23 14:41:58 MainProcess DEBUG: There is already a database connection active. 2022-05-23 14:42:36 MainProcess DEBUG: There is already a database connection active. 2022-05-23 14:44:37 MainProcess INFO: Initialising the replica for source mysql 2022-05-23 14:44:37 MainProcess DEBUG: starting init replica for source mysql 2022-05-23 14:44:37 MainProcess DEBUG: There is already a database connection active. 2022-05-23 14:44:37 MainProcess DEBUG: Collecting schema mappings for source mysql 2022-05-23 14:44:37 MainProcess DEBUG: mysql version 5007038 2022-05-23 14:44:37 MainProcess INFO: deleting all the table references from the replica catalog for source mysql  2022-05-23 14:44:37 MainProcess DEBUG: Creating the loading schema _sch_mysql57_test_tmp. 2022-05-23 14:44:37 MainProcess DEBUG: Creating the destination schema sch_mysql57_test. 2022-05-23 14:44:37 reader-3 INFO: Copying the source table tb_customer into _sch_mysql57_test_tmp.tb_customer 2022-05-23 14:44:37 reader-3 DEBUG: estimating rows in db_mysql57_test.tb_customer 2022-05-23 14:44:37 reader-3 DEBUG: The table db_mysql57_test.tb_customer will be copied in 1  estimated slice(s) of 256 rows, using a transaction True 2022-05-23 14:44:37 reader-3 DEBUG: locking the table `db_mysql57_test`.`tb_customer` 2022-05-23 14:44:37 reader-3 DEBUG: collecting the master's coordinates for table `db_mysql57_test`.`tb_customer` 2022-05-23 14:44:37 reader-3 DEBUG: Executing query for table db_mysql57_test.tb_customer 2022-05-23 14:44:37 reader-3 DEBUG: set isolation level 2022-05-23 14:44:37 reader-3 DEBUG: beginning transaction 2022-05-23 14:44:37 reader-3 DEBUG: unlocking the tables 2022-05-23 14:44:37 reader-3 DEBUG: rolling back 2022-05-23 14:44:38 writer-1 DEBUG: Building DDL for index PRIMARY 2022-05-23 14:44:38 writer-1 INFO: Building index pk_tb_customer_1653288278_0 on _sch_mysql57_test_tmp.tb_customer 2022-05-23 14:44:38 writer-2 DEBUG: Table db_mysql57_test.tb_customer copied 1 slice of 1 2022-05-23 14:44:38 MainProcess INFO: Swapping schema sch_mysql57_test with _sch_mysql57_test_tmp 2022-05-23 14:44:38 MainProcess DEBUG: Renaming schema sch_mysql57_test in _rename_sch_mysql57_test 2022-05-23 14:44:38 MainProcess DEBUG: Renaming schema _sch_mysql57_test_tmp in sch_mysql57_test 2022-05-23 14:44:38 MainProcess DEBUG: Renaming schema _rename_sch_mysql57_test in _sch_mysql57_test_tmp 2022-05-23 14:44:38 MainProcess DEBUG: Commit the swap transaction 2022-05-23 14:44:38 MainProcess DEBUG: Dropping the schema _sch_mysql57_test_tmp. 2022-05-23 14:44:38 MainProcess DEBUG: Changing the lock timeout for the session to 120s. 2022-05-23 14:44:38 MainProcess DEBUG: New log table : t_log_replica_mysql_2  2022-05-23 14:44:38 MainProcess INFO: Saved master data for source: mysql 2022-05-23 14:44:38 MainProcess DEBUG: Binlog file: mysql-bin.000002 2022-05-23 14:44:38 MainProcess DEBUG: Binlog position:154 2022-05-23 14:44:38 MainProcess DEBUG: Last event: None 2022-05-23 14:44:38 MainProcess DEBUG: Next log table name: t_log_replica_mysql_2 2022-05-23 14:44:38 MainProcess DEBUG: Next batch id: 1 2022-05-23 14:44:38 MainProcess INFO: Set high watermark for source: mysql 2022-05-23 14:44:38 MainProcess INFO: init replica for source mysql is complete 2022-05-23 14:53:26 MainProcess DEBUG: There is already a database connection active. 2022-05-23 14:53:26 MainProcess DEBUG: Collecting schema mappings for source mysql 2022-05-23 14:53:26 MainProcess INFO: retrieving foreign keys metadata for schemas 'db_mysql57_test' 2022-05-23 14:53:26 MainProcess DEBUG: There is already a database connection active. 2022-05-23 14:53:26 MainProcess DEBUG: Collecting schema mappings for source mysql 2022-05-23 14:53:26 MainProcess DEBUG: Deleting the source mysql  2022-05-23 14:53:26 MainProcess DEBUG: There is already a database connection active. ----------default_mysql.log 日志文件内容结束------------

1 0

current of 语法支持问题
by liuf＠geoscene.cn 19 May '22

19 May '22

您好： openGauss现在不支持update table where current of 语法问题，我看了下源码，这部分的代码是强制被关闭了，我打开之后发现单机是可以正常运行的，那当时关闭这部分代码是处于什么考虑呢，是因为分布式所以不支持了吗。刘锋易智瑞信息技术有限公司

1 0