May 2022 - Community - mailweb.opengauss.org

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

有关单节点和分布式部署
by tommy 18 May '22

18 May '22

下图提到的分布式OpenGauss：是不是就是下载页面上的这个： OpenGauss 同时提供单节点和分布式多节点两种部署模式吗？

2 3

请问如何修改opengauss 用户的密码？
by tommy 17 May '22

17 May '22

忘记了原来的密码，现在如何修改呢？ opengauss=# alter user opengauss identified by 'Opengauss123' REPLACE ''; ERROR: The old password is invalid. opengauss=# opengauss=# opengauss=# opengauss=# opengauss=# alter user opengauss identified by 'Opengauss123' REPLACE 'opengauss'; ERROR: The old password is invalid. opengauss=# opengauss=#

4 7

MOT页面、记录的内存结构，磁盘结构
by qinhao＠newland.com.cn 13 May '22

13 May '22

各位大佬好，我最近在学习OpenGauss MOT部分的代码，但是相关解释文档比较少，目前我比较感兴趣的是MOT记录在内存中的结构，是像Postgres那样页的格式吗？能够给予一些提示或文档，还有与MOT表对应的磁盘中的数据格式是怎样的？我问这些，是想看一下实现增删列定义的难度怎样，这是我们大概率用到的一个特性。新大陆软件秦浩 mobile: 17625988619 e-mail:qinhao@newland.com.cn

1 0

Re: [DISCUSS] Proposal for improving openGauss performance.
by pengjiong 12 May '22

12 May '22

Hi ` mysqlonarm`, thanks for your proposals, I think you'd better join the SIG conference, and introduce your idea to us, then we can understand you better. For incremental checkpoint part, I suggest you introduce it to the storage SIG, for unique sql part, I suggest you introduce it to the SQL SIG.

1 0

在存储过程和函数中，MOT表可以JOIN磁盘表？
by qinhao＠newland.com.cn 12 May '22

12 May '22

今天，在存储过程中使用MOT表时，发现MOT表可以JOIN磁盘表，文档中说MOT不支持跨引擎查询，在gsql终端查询MOT和磁盘表做JOIN报错，但是把跨引擎查询的SQL放在存储过程或者函数中，发现是可以正常执行的，在plpgsql语句块里也是可以的。这个功能对我们是有用的，是不是说，可以一把MOT跨引擎查询放在plpgsql代码块里？或者这是个bug？下面是我的测试用例： create table emp1( empno int primary key, ename varchar(10), job varchar(9), deptno numeric(2)); INSERT INTO emp1 VALUES (1,'SMITH','CLERK',20); INSERT INTO emp1 VALUES (2,'ALLEN','SALESMAN',10); INSERT INTO emp1 VALUES (3,'WARD','SALESMAN',30); create foreign table emp1mot( empno int primary key, ename varchar(10), job varchar(9), deptno numeric(2)); INSERT INTO emp1mot VALUES (1,'SMITH','CLERK',60); INSERT INTO emp1mot VALUES (2,'ALLEN','SALESMAN',50); INSERT INTO emp1mot VALUES (3,'WARD','SALESMAN',40); INSERT INTO emp1mot VALUES (4,'JONES','MANAGER',30); INSERT INTO emp1mot VALUES (5,'JONES','MANAGER',20); CREATE OR REPLACE PROCEDURE proc1() AS DECLARE rec record; BEGIN for rec in (select * from emp1 e1 join emp1mot e1m on e1.deptno = e1m.deptno) loop RAISE NOTICE '%, %, %, %', rec."empno", rec."ename", rec."job", rec."deptno"; end loop; END; / call proc1(); 新大陆软件秦浩 mobile: 17625988619 e-mail:qinhao@newland.com.cn

1 0

2024

2023

2022

2021

2020

Community May 2022