Versions

openGauss 3.1.0 is the preview version released by openGauss in 2022. The lifecycle of this version is 0.5 years. This document applies only to the enterprise edition.

The 3.1.0 version is compatible with the earlier versions. Main functions are as follows:

• Inherited functions:

  • SQL standard syntax, UPSERT, data type, XML type, table, temporary table, global temporary table, foreign table, view, materialized view, index, foreign key, generalized inverted index (GIN), sequence, function, trigger, ROWNUM, MEDIAN aggregate function, JSONB data type, GB18030 character set and UPSERT subquery, and row-store execution to vectorized execution.
  • Stored procedure, commit/rollback in stored procedure, omission of parameter parentheses () from the stored procedure or function calling, stored procedure debugging, and autonomous transaction.
  • Security features such as authentication, permission management, network communication security, database audit, fully encrypted database, dynamic masking, Chinese national cryptographic algorithm, tamper-proof ledger database, built-in role and permission management, transparent encryption, and ANY permission management.
  • HA functions such as primary/standby two-node cluster, cascaded standby node, logical replication, ultimate RTO, standby node scale-out, and Paxos-based distributed consensus framework (DCF).
  • Range partitioning, global partitioned indexes, list partitioning, hash partitioning, and interval partitioning (automatic partitioning based on range partitioning).
  • Full physical backup, logical backup, standby node backup, incremental backup and restoration, and point-in-time recovery (PITR).
  • Memory-optimized table (MOT), NUMA-aware high-performance capability, parallel query, and Global Syscache.
  • AI capabilities: parameter self-tuning, slow SQL discovery, Predictor (prediction of AI query time), Anomaly-detection (database metric collection, forecast, and exception detection), DBMind componentization, DeepSQL (in-database AI algorithms), as well as XGBoost, multiclass, and PCA supported by in-database AI algorithms.
  • Storage features such as delayed standby node replay, logical replication on standby nodes, Xlog archiving on standby nodes, parallel logical decoding, gray upgrade, hash index, unique primary key constraint for column-store tables, Ustore storage engine, segment-page storage, publication-subscription, and row-store table compression.
  • Database running metrics in WDRs, intelligent index recommendation enhancement, and automatic eviction of unique SQL statements.
  • Load balancing and read/write isolation on the JDBC client. It supports dblink, Ubuntu, CMake script compilation, container-based deployment, IPv6 protocol, and postgis plug-ins.
  • CM cluster management
  • Toolchains: DataStudio development tool and Chameleon data migration tool.
  • Middleware: ShardingSphere, Kubernetes, and openLookeng.

• New functions:

  • The performance of basic operators is improved. (For details, see the feature description.)
  • Two-City Three-DC DR is supported.
  • The CM supports external status query and push.
  • The DCF supports policy-based majority.
  • DBMind autonomous O&M platform is supported.
  • Intelligent optimizer is supported.
  • The fine-grained Any permission is enhanced.
  • The compression capability of row-store tables is enhanced.
  • Publication and subscription capabilities are enhanced.
  • Fine-grained rolling upgrade is supported.
  • The diagnosis capability of the statement_history view is enhanced.
  • Middleware: integrates OpenLookeng to provide distributed OLAP capabilities.
  • Middleware: The CM can manage the ShardingSphere Proxy and registration center.
  • Toolchain: MySQL full migration supports parallel migration, improving full migration performance.
  • Toolchain: MySQL incremental migration supports transaction-level parallel consumption, improving incremental migration performance.
  • Toolchain: The data verification based on the Merkle tree is supported.
  • Toolchain: Migration from openGauss to MySQL is supported, meeting MySQL reverse migration requirements.
  • Compatibility: Compatible with most common MySQL syntax, including data types, operators, system functions, DDL, DML, and DCL.

• Fixed defects:

  • I5LATD: When query_dop is set to 4, an error is reported when a query containing cube and Windows is executed.
  • I5RWR4: After the 2.0.4-3.1.0 gray upgrade is successfully rolled back, the rollback fails and an error is reported.
  • I5E52H: In a column-store table that contains long columns, the “could not open relation with OID” error may be reported after DML and vacuum deltamerge.
  • I5FQHH: Read-only status is lost after the CM cluster is restarted.
  • I5N6E6: After work_mem is set to 4MB and try_vector_engine_strategy is set to force, a core dump occurs when a complex subquery is executed.
  • I5LI7Y: When query_dop is set to 1, an error is reported during FULL JOIN query. When query_dop is set to 4, no error is reported.
  • I5MM6P: After parallel parsing is enabled, an LSN error is returned in the case of multiple transactions. As a result, data is parsed repeatedly after the application is restarted.
  • I53M9A: TYPE IS TABLE OF prints garbled GBK characters in the GBK environment.
  • I56S1E: When the column type in the database table is tinyint, the data type obtained by the cursor is str.
  • I5FIZ1: After the try_vector_engine_strategy parameter is set to force, a table is created, and an incremental materialized view is created, the result of querying the materialized view is incorrect.
  • I5E46Z: When -p is left blank or the port number is incorrect in the assessment statement, the error message is incorrect.
  • I5EOSI: The migration tool fails to migrate data online, and the migration tool page keeps refreshing.
  • I5EDAR: When a user-defined function is migrated, the function body contains return, and an error is reported during migration.
  • I5E4CE: When max_sync_workers_per_subscription is set to 0, no message is displayed indicating that basic data cannot be synchronized.
  • I5EDVY: After data is inserted into a table online, the data is not synchronized to openGauss. After another table is created, the data is migrated to openGauss.
  • I56B7E: When LIKE.. EXCLUDING is used to create a table, there is no row-store compression parameter.